16.1 Short message service point to point on CS mode

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

All of test cases in this clause are applied to UE supporting CS mode.

16.1.1 SMS mobile terminated

16.1.1.1 Definition

16.1.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 speech or data call in progress. A report will always be returned to the SC, confirming that the UE has received the short message.

Reference

3GPP TS 23.040 clause 3.1.

16.1.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.1.1.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– 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 call control state U10.

Maximum number of retransmissions of an unacknowledged CP-DATA message.

Test procedure

a) The UE terminates the establishment of Radio Resource Connection. After the completion of the RRC Connection the SS authenticates the UE.

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 of T3240) 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 data or speech call is established on a DTCH with the SS and the state U10 of call control 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. SS will wait for a period of 120ms. for the UE to send acknowledgement to the CP-ACK prior to the SS initiating the DISCONNECT. 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 of T3240) 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 a call in progress).

k) A data or speech call is established on a DTCH with the SS and the state U10 of call control shall be entered. The speech call is cleared by the SS with a disconnect message. (The call clearing is continued on the DCCH 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 data or speech call is established with the SS and the state U10 of call control is entered. The speech call shall be cleared from the UE. (The call clearing 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
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS 34.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	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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 TS 34.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	–>		PAGING RESPONSE
17	<–		AUTHENTICATION REQUEST
18	–>		AUTHENTICATION 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 TS 34.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	–>		PAGING RESPONSE
33	<–		AUTHENTICATION REQUEST
34	–>		AUTHENTICATION 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 of T3240) from step 41.
47			(void)
48	UE			The UE shall indicate that an SM has arrived.
49	SS			Following steps are applicable only for UE which supports CS call establishment (ICS pc_CS_CallEst). A data or speech call is established on a DTCH and the state U10 of call control 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
56a	SS			SS will wait for 120 ms for the ACK SUFI.
57	<–		DISCONNECT	Disconnect the active call
58	–>		RELEASE
58a			RELEASE COMPLETE
58b	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	SS			A data or speech call is established on a DTCH and the state U10 of call control 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
70a	SS			SS will wait for 120 ms for the ACK SUFI.
71	<–		DISCONNECT	Disconnect the active call
72	–>		RELEASE
73			RELEASE COMPLETE
74	SS			The SS releases the RRC connection
75	UE			The UE shall indicate that an SM has arrived.
76	UE			Clear the SMS message store
77	SS			A data or speech call is established on a DTCH and the state U10 of call control is entered.
78			(void)
79	<–		CP-DATA	Contains RP-DATA RPDU (SMS DELIVER TPDU)
80	SS			Waits max 25 s for CP-ACK
81	–>		CP-ACK
82	SS			Waits max 60 s for RP-ACK RPDU
83	–>		CP-DATA	First CP-DATA from UE, contains RP-ACK RPDU
84	SS			First CP-DATA message not acknowledged by SS
85	–>		CP-DATA	Retransmitted CP-DATA message within twice TC1M after step 83, contains RP-ACK RPDU
86	SS			Retransmitted CP-DATA message not acknowledged by SS
87	UE			Depending on the maximum number of CP-DATA retransmissions implemented, step 85-86 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.
87a			DISCONNECT	Disconnect the active call
87b			RELEASE
87c			RELEASE COMPLETE
88			(void)
89	SS			The SS releases the RRC connection after a duration of 4*TC1M + 10 s (Maximum of T3240) from step 83.
90	UE			The UE shall indicate that an SM has arrived.
91	UE			Clear the SMS message store
92	SS			A data or speech call is established on a DTCH and the state U10 of call control is entered.
93			(void)
94	<–		DISCONNECT	The speech call is cleared by the SS. The call clearing is continued in parallel to the following exchange of messages related to SMS.
95	<–		CP-DATA	Contains RP-DATA RPDU (SMS DELIVER TPDU)
96			void
96a			RELEASE	UE releases the connection
96b			RELEASE COMPLETE	SS completes the connection release (Step 96a and 96b may be executed after step 97)
97	–>		CP-ACK
			Void
98	SS			Waits max 60 s for RP-ACK RPDU
99	–>		CP-DATA	Contains RP-ACK RPDU
100	<–		CP-ACK
101	SS			The SS releases the RRC connection.
102	UE			The UE shall indicate that an SM has arrived.
103	UE			Clear the SMS message store
104	SS			A data or speech call is established on a DTCH and the state U10 of call control is entered.
105			(void)
106	–>		DISCONNECT	The speech call is cleared from the UE. The call clearing is continued in parallel to the following exchange of messages related to SMS.
107	<–		CP-DATA	Contains RP-DATA RPDU (SMS DELIVER TPDU)
108	<–		RELEASE	This message is likely to be sent before all of the CP-DATA message has been sent on the DCCH.
109	–>		RELEASE COMPLETE
110	–>		CP-ACK	shall be sent before 25 s after the start of step 107
111	SS			Waits max 60 s for RP-ACK RPDU
112	–>		CP-DATA	Contains RP-ACK RPDU
113	<–		CP-ACK
114	SS			The SS releases the RRC connection
115	UE			The UE shall indicate that an SM has arrived.
116	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.1.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 sending CP-ACK.

After step 14 UE shall indicate that an SM has arrived.

After step 25 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 sending CP-ACK.

After step 59 UE shall indicate that an SM has arrived.

After step 67 UE shall retransmit CP-DATA containing RP-ACK within twice TC1M.

After step 75 UE shall indicate that an SM has arrived.

After step 79 UE shall repeat CP-DATA retransmissions and the maximum number of retransmissions must not exceed three.

After step 90 UE shall indicate that an SM has arrived.

After step 95 UE shall receive SMS-DELIVER TPDU and send CP-ACK within 25 s and CP-DATA containing RP-ACK within 60 s after sending CP-ACK.

After step 102 UE shall indicate that an SM has arrived.

After step 107 UE shall receive SMS-DELIVER TPDU and send CP-ACK within 25 s and CP-DATA containing RP-ACK within 60 s after sending CP-ACK.

After step 115 UE shall indicate that an SM has arrived.

16.1.2 SMS mobile originated

16.1.2.1 Definition

16.1.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 speech or data call in progress.

Reference

3GPP TS 23.040 clause 3.1.

16.1.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.1.2.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– the SMS message storage shall be empty.

Related ICS/IXIT Statements

Support for Short message MO/PP.

Support for state U10 of call control.

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 of T3240) 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.

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 data or speech call is established with the SS and the state U10 of call control is entered. The UE is set up to send an SM to the SS. After the reception of the CM SERVICE REQUEST, the SS sends a CM SERVICE ACCEPT message.

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 of T3240) 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 call in progress).

j) (void)

k) The UE is set up to send an SM to the SS. On receipt of the CM SERVICE REQUEST the SS sends a CM SERVICE REJECT message with the reject cause set to "Service Option not supported" or "Service Option temporarily out of order". After 5 s the SS initiates RRC connection release.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
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	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service"
6	<–		AUTHENTICATION REQUEST
7	–>		AUTHENTICATION 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	UE			The UE is set up to send an SM
17	SS			The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Low Priority Signalling”.
18			Void
19			Void
20			Void
21			Void
22	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service"
23	<–		AUTHENTICATION REQUEST
24	–>		AUTHENTICATION RESPONSE
25	<–		SECURITY MODE COMMAND
26	–>		SECURITY MODE COMPLETE
27	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU)
28	SS			SS configured not to send CP-ACK
29	–>		CP-DATA	Retransmitted CP-DATA message within twice TC1M after step 27
30	UE			Depending on the maximum number of CP-DATA retransmissions implemented, step 29 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.
30aa	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.
30a	SS			The SS releases the RRC connection after a duration of 4*TC1m + 10 s (Maximum of T3240) from step 27.
30b			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			(void)
37	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service"
38	<–		AUTHENTICATION REQUEST
39	–>		AUTHENTICATION RESPONSE
40	SS			The SS starts integrity protection
41			(void)
42	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU)
43	<–		CP-ERROR	Sent within TC1M containing "Network Failure" cause.
44	SS			The SS releases the RRC connection.
45			(void)
46	SS			Following steps are applicable only for UE which supports CS call establishment (ICS pc_CS_CallEst). A data or speech call is established on a DTCH and the state U10 of call control is entered.
47	UE			The UE is set up to send an SM
48	–>		CM SERVICE REQUEST	CM service type set to "short message "
49	<–		CM SERVICE ACCEPT
50	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU)
51	<–		CP-ACK	Sent within TC1M after step 50
52	<–		CP-DATA	Contains RP-ACK RPDU
53	SS			Waits max 25 s for CP-ACK
54	–>		CP-ACK
55	SS			The SS releases the RRC connection.
56			(void)
57	SS			A data or speech call is established on a DTCH and the state U10 of call control is entered.
57a	UE			The UE is set up to send an SM
58	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service", upon CP-DATA retransmission new RRC connection has to be established, see step 64a.
59	<–		CM SERVICE ACCEPT
60	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU)
61	SS			SS configured not to send CP-ACK
62	–>		CP-DATA	Retransmitted CP-DATA message within twice TC1M after step 60
63	UE			Depending on the maximum number of CP-DATA retransmissions implemented, step 62 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.
63a			(void)
64	SS			The SS releases the RRC connection after a duration of 4*TC1m + 10 s (Maximum of T3240) from step 60.
64a			(void)
65			(void)
66-78			(void)
79	UE			The UE is set up to send an SM
80	SS			The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Low Priority Signalling”.
81			(void)
82	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service"
83	<–		CM SERVICE REJECT	Reject cause set to "Service Option not supported" or "Service Option temporarily out of order"
84			(void)
85	SS			The SS releases the RRC connection. 5 s after CM SERVICE REJECT
86			(void)
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.1.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 27 UE shall retransmit a CP-DATA containing RP-data and the maximum number of retransmissions must not exceed three. The RP-DATA shall contain SMS SUBMIT TPDU.

After step 50 UE shall send a CP-DATA containing RP-data. The RP-DATA shall contain SMS SUBMIT TPDU.

After step 62 UE shall retransmit a CP-DATA containing RP-data and the maximum number of retransmissions must not exceed three. The RP-DATA shall contain SMS SUBMIT TPDU.

After step 85 UE shall not send any CP-DATA.

16.1.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.1.3.1 Definition

16.1.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.1.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.1.3.4 Method of test

Initial conditions

– System Simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– 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:

– EF_SMS with at least one record;

– EF_SMSS, with SMS "Memory Cap. Exceed" notification flag set to "memory available";

– Service no. 10 (SMS) in EF_UST 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.1.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
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
2	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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	–>		PAGING RESPONSE
17	<–		AUTHENTICATION REQUEST
18	–>		AUTHENTICATION 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 15-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	–>		PAGING RESPONSE
31	<–		AUTHENTICATION REQUEST
32	–>		AUTHENTICATION 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	–>		CM SERVICE REQUEST	CM service type information element is set to "Short message transfer".
49	<–		CM 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.1.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.1.4 Test of the status report capabilities and of SMS-COMMAND:

This test applies to UEs which support the status report capabilities.

16.1.4.1 Definition

16.1.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 clause 3.2.9.

– 3GPP TS 23.040 clauses 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.1.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.1.4.4 Method of test

Initial conditions

– System Simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated".

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.1.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
Step	UE	SS	Message	Comments
1	<–		SYSTEM INFORMATION	BCCH
2	–>		RRC CONNECTION REQUEST	CCCH
3	<–		RRC CONNECTION SETUP	CCCH
4	–>		RRC CONNECTION SETUP COMPLETE	DCCH
5	–>		CM SERVICE REQUEST
6	<–		AUTHENTICATION REQUEST
7	–>		AUTHENTICATION 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	–>		PAGING RESPONSE
19	<–		AUTHENTICATION REQUEST
20	–>		AUTHENTICATION 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	RRC connection is released.
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	–>		CM SERVICE REQUEST
35	<–		AUTHENTICATION REQUEST
36	–>		AUTHENTICATION 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	RRC connection is released.
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	–>		CM SERVICE REQUEST
50	<–		AUTHENTICATION REQUEST
51	–>		AUTHENTICATION 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	RRC connection is released.
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 "00000010"B
TP-MN	not checked (TP-MR in previous SMS-SUBMIT)

16.1.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.1.5 Test of message class 0 to 3

16.1.5.1 Short message class 0

16.1.5.1.1 Definition

16.1.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.1.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.1.5.1.4 Method of test

Initial conditions

– System Simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– 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.1.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.1.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
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
2	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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.1.3) with Class 1 SMS-DELIVER TPDU.
15			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
16	–>		PAGING RESPONSE
17	<–		AUTHENTICATION REQUEST
18	–>		AUTHENTICATION 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.1.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.1.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.1.5.2.1 Definition

16.1.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.1.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.1.5.2.4 Method of test

Initial conditions

– System Simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– 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.1.1, step a).

b) The Short Message is recalled (e.g. by means of the MMI).

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
2	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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.1.5.2.5 Test requirements

After step 7 UE shall store the message in the ME or USIM and send an acknowledgement.

16.1.5.3 Test of class 2 short messages

16.1.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.1.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.

– 3GPP TS 34.108 clause 8.3.2.28.

16.1.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.1.5.3.4 Method of test

Initial conditions

– System Simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– 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:

– EF_SMS with at least two free records and one full record;

– EF_SMSS, with SMS "Memory Cap. Exceed" notification flag set to "memory available";

– Service no. 10 (SMS) in EF_UST 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.1.1, step b).

b) Following an attempt by the ME to store the short message in a free record of EF_SMS 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 EF_SMS 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
Step	UE	SS	Message	Comments
1	<		Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
2	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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	–>		PAGING RESPONSE
17	<–		AUTHENTICATION REQUEST
18	–>		AUTHENTICATION 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.1.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 25 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.1.5.4 Test of class 3 short messages

For further study.

16.1.6 Test of short message type 0 (R99 and REL-4 UE)

16.1.6.1 Definition and applicability

This tests that the UE correctly acknowledges the receipt of the short message type 0 to the SC in Circuit 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 CS mode.

16.1.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.1.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.1.6.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

the UE shall be in MM-state "Idle, updated".

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.1.1 but with the TPDU described in this section.

Maximum Duration of Test

1 minute

Expected Sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
2	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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.1.6a Test of short message type 0 ( REL-5 UE)

16.1.6a.1 Definition and applicability

This tests that the UE correctly acknowledges the receipt of the short message type 0 to the SC in Circuit Switched mode. The UE shall discard the contents of the short message type 0.

This test shall apply to all  REL-5 UEs supporting receipt of short messages in CS mode.

16.1.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.1, 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.1.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.1.6a.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

User Equipment:

the UE shall be in MM-state "Idle, updated".

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.1.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.1.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
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
2	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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	–>		PAGING RESPONSE
17	<–		AUTHENTICATION REQUEST
18	–>		AUTHENTICATION 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.1.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.1.7 Test of the replace mechanism for SM type 1-7

16.1.7.1 Definition

16.1.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.1.7.3 Test purpose

This procedure verifies the correct implementation of the replace mechanism for Replace Short Messages.

16.1.7.4 Method of test

Initial conditions

– System Simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– 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.1.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) Void

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
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
2	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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	–>		PAGING RESPONSE
15	<–		AUTHENTICATION REQUEST
16	–>		AUTHENTICATION 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 RPOA, 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			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
38	–>		PAGING RESPONSE
39	<–		AUTHENTICATION REQUEST
40	–>		AUTHENTICATION 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	–>		PAGING RESPONSE
51	<–		AUTHENTICATION REQUEST
52	–>		AUTHENTICATION 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.1.7.5 Test requirements

After step 61 only the Short Messages delivered in step 7, 19 and 55 shall be retrieved and indicated.

16.1.8 Test of the reply path scheme

16.1.8.1 Definition

16.1.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.5, D.6.

NOTE: Annex D of 3GPP TS 23.040 is only informative.

16.1.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.1.8.4 Method of test

Initial conditions

– System Simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– 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.1.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
Step	UE	SS	Message	Comments
1			Mobile terminated establishment of Radio Resource Connection	See 3GPP TS34.108
2	–>		PAGING RESPONSE
3	<–		AUTHENTICATION REQUEST
4	–>		AUTHENTICATION 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	–>		PAGING RESPONSE
15	<–		AUTHENTICATION REQUEST
16	–>		AUTHENTICATION 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	–>		CM SERVICE REQUEST
31	<–		AUTHENTICATION REQUEST
32	–>		AUTHENTICATION 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.
40A	–>		RRC CONNECTION RELEASE COMPLETE
41	UE			UE establishes the RRC connection in order to send the Reply Short Message corresponding to other Short Message.
42	<–		SYSTEM INFORMATION	BCCH
43	–>		RRC CONNECTION REQUEST	CCCH
44	<–		RRC CONNECTION SETUP	CCCH
45	–>		RRC CONNECTION SETUP COMPLETE	DCCH

46	–>		CM SERVICE REQUEST
47	<–		AUTHENTICATION REQUEST
48	–>		AUTHENTICATION RESPONSE
49	<–		SECURITY MODE COMMAND
50	–>		SECURITY MODE COMPLETE
51	–>		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
52	<–		CP-ACK	Sent within TC1M after step 51
53	<–		CP-DATA	Contains RP-ACK RPDU
54	SS			Waits max 25 s for CP-ACK
55	–>		CP-ACK
56	<–		RRC CONNECTION RELEASE	RRC connection is released.
57	–>		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.1.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 51 UE shall send the Reply Short Message corresponding to the other of two previously received short messages.

16.1.9 Multiple SMS mobile originated

16.1.9.1 UE in idle mode

This test applies to UE supporting the ability of sending multiple short messages on the same RRC connection when there is no call in progress.

16.1.9.1.1 Definition

16.1.9.1.2 Conformance requirements

Release 1999:

If another short message or a memory available notification is to be sent, an originating SMR entity in the UE may choose to continue to use the same RRC connection. When the UE chooses to use the same RRC connection, then:

‑ the UE shall transmit a CM SERVICE REQUEST for the new CM connection before the final CP‑ACK (e.g. the one that acknowledges the CP‑DATA that carried the RP‑ACK) for the old MM connection is transmitted;

‑ before transmission of the first CP‑DATA on the new MM connection, the UE shall transmit the CP‑ACK for the old MM connection;

‑ the Transaction Identifier used on the new MM connection shall be different to that used on the old MM connection; and

‑ the UE shall not initiate establishment of the new MM connection before the final CP‑DATA (e.g. the one carrying the RP‑ACK) has been received.

Release 4 or later release:

In the case of a SMS transfer via the CS domain, when the UE chooses to use the same RR or CS signalling connection, then:

– the UE shall transmit a CM SERVICE REQUEST for the new CM connection before the final CP‑ACK (i.e. the one that acknowledges the CP‑DATA that carried the RP‑ACK) for the old MM connection is transmitted;

– before transmission of the first CP‑DATA on the new MM connection, the UE may transmit the CP‑ACK for the old MM connection; the UE shall not transmit the final CP-ACK after the new CP-DATA;

– the Transaction Identifier used on the new MM connection shall be different to that used on the old MM connection; and

– the UE shall not initiate establishment of the new MM connection before the final CP‑DATA (e.g. the one carrying the RP‑ACK) has been received.

References

– 3GPP TS 23.040 clause 3.1.

– 3GPP TS 24.011 clause 5.4.

16.1.9.1.3 Test purpose

To verify that the UE is able to correctly concatenate multiple short messages on the same RRC connection when using a DCCH.

16.1.9.1.4 Method of test

Initial conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– the SMS message storage shall be empty.

Related ICS/IXIT statements

Support for concatenation of multiple short messages MO/PP on the same RRC connection.

Description of how to enter multiple SMS.

Whether SMS messages are stored in the USIM and/or the ME.

Foreseen final state of UE

Idle, updated.

Test procedure

a) The UE shall be set up to send 3 short messages as multiple SM to the SS. The UE establishes successfully an RRC connection and then the SS performs the authentication.

b) 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 followed by a CP-DATA message containing the correct RP-ACK RPDU. The Transaction Identifier used on this MM connection is ‘x’.

d) The UE shall transmit a CM SERVICE REQUEST for the new CM connection (for the second short message) before the final CP-ACK (the one that acknowledges the CP-DATA that carried the RP-ACK before) for the old MM connection is transmitted. The UE shall not initiate establishment of the new MM connection before the final CP-DATA (i.e. the one carrying the RP-ACK for the first short message) has been received. Before transmission of the first CP-DATA on the new MM connection:

– For R99: The UE shall transmit the CP-ACK for the old MM connection. The Transaction Identifier used on the new MM connection shall be y, where y <> x (see step c)). Thereby, the UE can transmit the final CP-ACK after either the sending of the CM SERVICE REQUEST for the new CM connection or the reception of the CM SERVICE ACCEPT for the new CM connection, thus two branches for the transmission of the final CP-ACK are possible which are specified in the expected sequence table like A and B respectively. The SS waits for the UE to transmit the final CP-ACK. If received within 5 s then the SS transmits the CM SERVICE ACCEPT and waits for the UE to transmit the first CP-DATA on the new MM connection (branch A). If the final CP-ACK is not received within 5 s then the SS transmits the CM SERVICE ACCEPT and waits for the UE to send the final CP-ACK followed by the first CP-DATA on the new MM connection (branch B).

– For Rel-4 or later release: The UE may transmit the CP-ACK for the old MM connection. The Transaction Identifier used on the new MM connection shall be y, where y <> x (see step c)). Thereby, the UE can transmit the final CP-ACK after either the sending of the CM SERVICE REQUEST for the new CM connection or the reception of the CM SERVICE ACCEPT for the new CM connection or not to send a CP-ACK at all, thus three cases are possible. These cases are specified using two branches for the transmission of the final CP-ACK where the transmission of the final CP-ACK for the old MM connection is optional. The two branches are specified in the expected sequence table like A and B respectively. The SS waits for the UE to transmit the final CP-ACK. If received within 5 s then the SS transmits the CM SERVICE ACCEPT and waits for the UE to transmit the first CP-DATA on the new MM connection (branch A). If the final CP-ACK is not received within 5 s then the SS transmits the CM SERVICE ACCEPT and then waits for the UE to send the final CP-ACK (optional) and/or the first CP-DATA on the new MM connection (branch B).

e) Void.

f) The SS responds to the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the UE with a CP‑ACK message followed by a CP-DATA message containing the correct RP-ACK RPDU.

g) The UE shall transmit a CM SERVICE REQUEST for the new CM connection (for the third short message) before the final CP-ACK (the one that acknowledges the CP-DATA that carried the RP-ACK before) for the old MM connection is transmitted. Before transmission of the first CP-DATA on the new MM connection:

– For R99: The UE shall transmit the CP-ACK for the old MM connection. The Transaction Identifier used on the new MM connection shall be z, where z <> y (see step d)). The UE shall not initiate establishment of the new MM connection before the final CP-DATA (i.e. the one carrying the RP-ACK for the second short message) has been received. Thereby, the UE can transmit the final CP-ACK after either the sending of the CM SERVICE REQUEST for the new CM connection or the reception of the CM SERVICE ACCEPT for the new CM connection, thus two branches for the transmission of the final CP-ACK are possible which are specified in the expected sequence table like A and B respectively. The SS waits for the UE to transmit the final CP-ACK. If received within 5 s then the SS transmits the CM SERVICE ACCEPT and waits for the UE to transmit the first CP-DATA on the new MM connection (branch A). If the final CP-ACK is not received within 5 s then the SS transmits the CM SERVICE ACCEPT and waits for the UE to send the final CP-ACK followed by the first CP-DATA on the new MM connection (branch B).

– For Rel-4 or later release: The UE may transmit the CP-ACK for the old MM connection. The Transaction Identifier used on the new MM connection shall be z, where z <> y (see step d)). Thereby, the UE can transmit the final CP-ACK after either the sending of the CM SERVICE REQUEST for the new CM connection or the reception of the CM SERVICE ACCEPT for the new CM connection or not to send a CP-ACK at all, thus three cases are possible. These cases are specified using two branches for the transmission of the final CP-ACK where the transmission of the final CP-ACK for the old MM connection is optional. The two branches are specified in the expected sequence table like A and B respectively. The SS waits for the UE to transmit the final CP-ACK. If received within 5 s then the SS transmits the CM SERVICE ACCEPT and waits for the UE to transmit the first CP-DATA on the new MM connection (branch A). If the final CP-ACK is not received within 5 s then the SS transmits the CM SERVICE ACCEPT and then waits for the UE to send the final CP-ACK (optional) and/or the first CP-DATA on the new MM connection (branch B).

h) Void.

i) The SS responds to the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the UE with a CP‑ACK message followed by a CP-DATA message containing the correct RP-ACK RPDU.

j) The SS waits a maximum of 5 s after sending CP-DATA for the CP-ACK message from the UE.

k) The SS sends a RRC CONNECTION RELEASE to the UE.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	UE			The UE is set up to send 3 short messages as multiple 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	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service".
6	<–		AUTHENTICATION REQUEST
7	–>		AUTHENTICATION RESPONSE
8	SS			The SS starts integrity protection
9			Void
10	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 10, 11, 12 and 14 shall be x.
11	<–		CP-ACK
12	<–		CP-DATA	Contains RP-ACK RPDU
13	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service".
14	–>		CP-ACK	The one that acknowledges the CP-DATA which carried the RP-ACK RPDU. If CP-ACK received then continue at A15 If CP-ACK is not received within 5 s from the CM SERVICE REQUEST was sent in step 13 then goto step B15a. (See note 1 and note 2)
Branch A
A15	<–		CM SERVICE ACCEPT	After having sent the CM SERVICE ACCEPT then goto step 16.
Branch B
B15a	<–		CM SERVICE ACCEPT
B15b	–>		CP-ACK	The one that acknowledges the CP-DATA which carried the RP-ACK RPDU. For Rel-4 or later release UE: Optional step (See note 2)
16	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 16, 17, 18 and 20 shall be y where y <> x (see step 10).
17	<–		CP-ACK
18	<–		CP-DATA	Contains RP-ACK RPDU
19	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service".
20	–>		CP-ACK	The one that acknowledges the CP-DATA which carried the RP-ACK RPDU. If CP-ACK received then continue at A21 If CP-ACK is not received within 5 s from the CM SERVICE REQUEST was sent in step 19 then goto step B21a. (See note 1 and note 2)
Branch A
A21	<–		CM SERVICE ACCEPT	After having sent the CM SERVICE ACCEPT then goto step 22.
Branch B
B21a	<–		CM SERVICE ACCEPT
B21b	–>		CP-ACK	The one that acknowledges the CP-DATA which carried the RP-ACK RPDU. For Rel-4 or later release UE: Optional step (See note 2)
22	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 22, 23, 24 and 25 shall be z, where z <> y (see step 16).
23	<–		CP-ACK
24	<–		CP-DATA	Contains RP-ACK RPDU
25	–>		CP-ACK	Shall be sent within 5 s of step 24
26	SS			The SS releases the RRC connection
NOTE 1: 5 s have been agreed to be a reasonable value to secure that the UE have enough time to respond to the different messages. NOTE 2: The CP-ACK for the old MM connection can be received either before or after the reception of the CM SERVICE ACCEPT message. For Release 4 or later release the UE transmission of the final CP-ACK is optional.

16.1.9.1.5 Test requirements

In step 13 the UE shall transmit a CM SERVICE REQUEST for the new CM connection (for the second short message) before the final CP-ACK for the old MM connection is transmitted.

In step 19 the UE shall transmit a CM SERVICE REQUEST for the new CM connection (for the third short message) before the final CP-ACK for the old MM connection is transmitted.

16.1.9.2 UE in active mode

This test applies to UE supporting the ability of sending concatenated multiple short messages when there is a call in progress.

16.1.9.2.1 Definition

16.1.9.2.2 Conformance requirements

Release 1999:

‑ before transmission of the first CP‑DATA on the new MM connection, the UE shall transmit the CP‑ACK for the old MM connection;

‑ the Transaction Identifier used on the new MM connection shall be different to that used on the old MM connection; and

‑ the UE shall not initiate establishment of the new MM connection before the final CP‑DATA (e.g. the one carrying the RP‑ACK) has been received.

Release 4 or later release:

In the case of a SMS transfer via the CS domain, when the UE chooses to use the same RR or CS signalling connection, then:

– before transmission of the first CP‑DATA on the new MM connection, the UE may transmit the CP‑ACK for the old MM connection; the UE shall not transmit the final CP-ACK after the new CP-DATA;

– the Transaction Identifier used on the new MM connection shall be different to that used on the old MM connection; and

– the UE shall not initiate establishment of the new MM connection before the final CP‑DATA (e.g. the one carrying the RP‑ACK) has been received.

References

– 3GPP TS 23.040 clause 3.1.

– 3GPP TS 24.011 clause 5.4.

16.1.9.2.3 Test purpose

To verify that the UE is able to correctly concatenate multiple short messages on the same RRC connection when sent parallel to a call.

16.1.9.2.4 Method of test

Initial conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– the SMS message storage shall be empty.

Related ICS/IXIT statements

Support for concatenation of multiple short messages MO/PP on the same RRC connection.

Description of how to enter multiple SMS.

Support for state U10 of call control.

Whether SMS messages are stored in the USIM and/or the ME.

Foreseen final state of UE

Idle, updated.

Test procedure

a) A data or speech call is established on a DTCH with the SS and the state U10 of call control is entered. The UE is set up to send 3 short messages as multiple SM to the SS. After the reception of the CM SERVICE REQUEST, the SS sends a CM SERVICE ACCEPT message.

b) Steps c) to k) of the test procedure in clause 16.1.9.1.4 are repeated.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	SS			A data or speech call is established on a DTCH and the state U10 of call control is entered.
2	UE			The UE is set up to send 3 short messages as multiple SM
3	–>		CM SERVICE REQUEST	Sent in a layer 2 frame on the DCCH. CM service type set to "Short Message Service"
4	<–		CM SERVICE ACCEPT
7	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 7, 8, 9 and 11 shall be x.
8	<–		CP-ACK
9	<–		CP-DATA	Contains RP-ACK RPDU
10	–>		CM SERVICE REQUEST	Sent in a layer 2 frame on the DCCH. CM service type set to "Short Message Service"
11	–>		CP-ACK	The one that acknowledges the CP-DATA which carried the RP-ACK RPDU. If CP-ACK received then continue at A12 If CP-ACK is not received within 5 s from the CM SERVICE REQUEST was sent in step 10 then goto step B11. (See note 1 and note 2)
Branch A
A12	<–		CM SERVICE ACCEPT	After having sent the CM SERVICE ACCEPT then goto step 13.
Branch B
B11	<–		CM SERVICE ACCEPT
B12	–>		CP-ACK	The one that acknowledges the CP-DATA which carried the RP-ACK RPDU. For Rel-4 or later release UE: Optional step (See note 2)
13	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 13, 14, 15 and 17 shall be y where y <> x (see step 7).
14	<–		CP-ACK
15	<–		CP-DATA	Contains RP-ACK RPDU
16	–>		CM SERVICE REQUEST	Sent in a layer 2 frame on the DCCH. CM service type set to "Short Message Service"
17	–>		CP-ACK	The one that acknowledges the CP-DATA which carried the RP-ACK RPDU. If CP-ACK received then continue at A18. If CP-ACK is not received within 5 s from the CM SERVICE REQUEST was sent in step 16 then goto step B17. (See note 1 and note 2)
Branch A
A18	<–		CM SERVICE ACCEPT
Branch B
B17	<–		CM SERVICE ACCEPT
B18	–>		CP-ACK	The one that acknowledges the CP-DATA which carried the RP-ACK RPDU. For Rel-4 or later release UE: Optional step (See note 2)
19	–>		CP-DATA	Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 19, 20, 21 and 22 shall be z, where z <> y (see step 13).
20	<–		CP-ACK
21	<–		CP-DATA	Contains RP-ACK RPDU
22	–>		CP-ACK	Shall be sent within 5 s of step 21
23	SS			The SS releases the RRC connection
NOTE 1: 5 s have been agreed to be a reasonable value to secure that the UE have enough time to respond to the different messages. NOTE 2: The CP-ACK for the old MM connection can be received either before or after the reception of the CM SERVICE ACCEPT message. For Release 4 or later release the UE transmission of the final CP-ACK is optional.

16.1.9.2.5 Test requirements

In step 10 the UE shall transmit a CM SERVICE REQUEST for the new CM connection (for the second short message) before the final CP-ACK for the old MM connection is transmitted.

In step 16 the UE shall transmit a CM SERVICE REQUEST for the new CM connection (for the third short message) before the final CP-ACK for the old MM connection is transmitted.

16.1.10 Test of capabilities of simultaneously receiving a short message whilst sending a mobile originated short message

16.1.10.1 Definition

16.1.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 clauses 3.1, 9.2.3.16.

3GPP TS 24.011 clause 3.2.

16.1.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.1.10.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

– the SMS message storage shall be empty.

Related ICS/IXIT Statements

Support for Short message MO/PP and MT/PP.

Support for state U10 of call control.

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.1.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
Step	UE	SS	Message	Comments
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	–>		CM SERVICE REQUEST	CM service type set to "Short Message Service"
6	<–		AUTHENTICATION REQUEST
7	–>		AUTHENTICATION RESPONSE
8	SS			The SS starts integrity protection
9			(void)
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.1.10.5 Test requirements

After step 12 UE shall correctly receive the SM and indicate that a message has arrived.