6.6A Default SMS over SGs message and information element contents

36.5083GPPCommon test environments for User Equipment (UE) conformance testingEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Release 17TS

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

The default SMS over SGs message and information element contents specified in this subclause apply to all SMS over SGs Signalling test cases defined in TS 36.523-1 [18] unless otherwise specified. All the messages and information elements are listed in alphabetical order.

6.6A.1 CM-sublayer messages

– CP-ACK

This message is sent between the SS and the UE, in both directions.

Table 6.6A.1-1: Message CP-ACK

Derivation Path: 24.011 clause 7.2.2
Information Element	Value/remark	Comment	Condition
Protocol discriminator	‘1001’B	SMS messages
Transaction identifier	Any allowed value
Message type	‘00000100’B	CP-ACK

– CP-DATA

This message is sent between the SS and the UE, in both directions.

Table 6.6A.1-2: Message CP-DATA

Derivation Path: 24.011 clause 7.2.1
Information Element	Value/remark	Comment	Condition
Protocol discriminator	‘1001’B	SMS messages
Transaction identifier	Any allowed value
Message type	‘00000001’B	CP-DATA
CP-User data	RP-ACK RPDU or RP-DATA RPDU (as specified in the test case)

6.6A.2 Short Message Relay Layer (SM-RL) messages

– RP-ACK RPDU

This message is sent between the SS and the UE, in both directions.

Table 6.6A.2-1: Message RP-ACK RPDU

Derivation Path: 24.011 clause 7.3.3
Information Element	Value/remark	Comment	Condition
RP‑Message Type	‘010’B	RP-ACK_PDU uplink	Uplink_SMS
	‘011’B	RP-ACK_PDU downlink	Downlink_SMS
RP‑Message Reference	Same as in associated (preceding) RP-DATA RPDU
RP-User Data	Not present or any allowed value		Uplink_SMS
	Not present		Downlink_SMS

Condition	Explanation
Uplink_SMS	This condition applies when the message is sent by the UE to the SS.
Downlink_SMS	This condition applies when the message is sent by the SS to the UE.

– RP-DATA RPDU

This message is sent between the SS and the UE, in both directions.

Table 6.6A.2-2: Message RP-DATA RPDU

Derivation Path: 24.301 clause 8.2.23
Information Element	Value/remark	Comment	Condition
RP‑Message Type	‘001’B	RP-DATA_PDU downlink	Downlink_SMS
	‘000’B	RP-DATA_PDU uplink	Uplink_SMS
RP‑Message Reference	Any allowed value
RP‑Originator Address	Any allowed value	originating Service Centre address	Downlink_SMS
	Not present		Uplink_SMS
RP‑Destination Address	Not present		Downlink_SMS
	Any allowed value	destination Service Centre address	Uplink_SMS
RP-User Data	SMS-SUBMIT or SMS-DELIVER (as set in the test case)

Condition	Explanation
Uplink_SMS	See the definition below table 6.6A.2-1.
Downlink_SMS	See the definition below table 6.6A.2-1.

6.6A.3 Short Message Transfer Layer (SM-TL) messages

– SMS-DELIVER

This message is sent by the SS to the UE.

Table 6.6A.3-1: Message SMS-DELIVER

Derivation Path: 23.040 clause 9.2.2.1
Information Element	Value/remark	Comment	Condition
TP-MTI	‘00’B	SMS-DELIVER
TP-MMS	‘1’B	No more messages are waiting for the MS in this SC
TP-RP	Any allowed value
TP-UDHI	‘0’B
TP-SRI	‘0’B
TP-OA	Any allowed value
TP-PID	‘00000000’B
TP-DCS	Any allowed value
TP-SCTS	Any allowed value
TP-UDL	160
TP-UD (140 octets)	text of message (160 characters)	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).

– SMS-SUBMIT

This message is sent by the UE to the SS.

Table 6.6A.3-2: Message SMS-SUBMIT

Derivation Path: 23.040 clause 9.2.2.2
Information Element	Value/remark	Comment	Condition
TP‑MTI	‘01’B	SMS‑SUBMIT
TP-RD	Any allowed value
TP-VPF	Any allowed value
TP-RP	Any allowed value
TP-UDHI	Not present or any allowed value
TP-SRR	Not present or any allowed value
TP-MR	Any allowed value
TP-DA	Any allowed value
TP-PID	‘00000000’B
TP-DCS	Any allowed value
TP-VP	Not present or any allowed value
TP-UDL	160
TP-UD (140 octets)	text of message (160 characters)