11.1 SMS over SGs

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

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

11.1.1 MT-SMS over SGs / Idle mode

11.1.1.1 Test Purpose (TP)

(1)

with { UE is IMSI attached for non-EPS services and UE has received a paging request with CN domain indicator set to "PS" in EMM-IDLE mode and UE has sent a SERVICE REQUEST message}

ensure that {
when { UE receives a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message }

then { UE sends a CP-ACK encapsulated in an Uplink NAS transport message followed by a CP-DATA containing an RP-ACK RPDU encapsulated in an Uplink NAS transport message}

}

11.1.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clauses 5.6.3.1, 5.6.3.3 and 9.9.3.22.

[TS 24.301, clause 5.6.3.1]

The purpose of the transport of NAS messages procedure is to carry SMS messages in an encapsulated form between the MME and the UE. The procedure may be initiated by the UE or the network and can only be used when the UE is attached for EPS services and IMSI attached for non-EPS services and is in EMM-CONNECTED mode.

[TS 24.301, clause 5.6.3.3]

The network initiates the procedure by sending a DOWNLINK NAS TRANSPORT message. When receiving the DOWNLINK NAS TRANSPORT message, the EMM entity in the UE shall forward the contents of the NAS message container IE to the SMS entity.

[TS 24.301, clause 9.9.3.22]

This information element is used to encapsulate the SMS messages transferred between the UE and the network. The NAS message container information element is coded as shown in figure 9.9.3.22.1 and table 9.9.3.22.1.

The NAS message container is a type 4 information element with a minimum length of 4 octets and a maximum length of 253 octets.

8	7	6	5	4	3	2	1
NAS message container IEI								octet 1
Length of NAS message container contents								octet 2
								octet 3
NAS message container contents
								octet n

Figure 9.9.3.22.1: NAS message container information element

Table 9.9.3.22.1: NAS message container information element

NAS message container contents (octet 3 to octet n)

This IE can contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in subclause 7.2 in 3GPP TS 24.011 [13A].

11.1.1.3 Test description

11.1.1.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18].

– Cell A belongs TAI-1.

– Cell A is set to the ”Serving cell”.

UE:

– The UE does not have any stored SMS message.

Preamble:

– UE is in state Registered, Idle Mode (state 2) on Cell A according to [18].

11.1.1.3.2 Test procedure sequence

Table 11.1.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS pages the UE using S-TMSI with CN domain indicator set to ”PS’.	–	–	–	–
2	The UE transmits a SERVICE REQUEST message.	–>	SERVICE REQUEST	–	–
3	The SS transmits a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message to the UE.	<–	DOWNLINK NAS TRANSPORT	–	–
4	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	1	P
5	Check: Does the UE transmit a CP-DATA containing an RP-ACK RPDU encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	1	P
6	The SS transmits a CP-ACK encapsulated in a Downlink NAS transport message to the UE.	<–	DOWNLINK NAS TRANSPORT	–	–

11.1.1.3.3 Specific message contents

Table 11.1.1.3.3-1: Message DOWNLINK NAS TRANSPORT (step 3, Table 11.1.1.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.1.3.3-2: Message CP-DATA (step 3, Table 11.1.1.3.2-1)

Information Element	Value/remark	Comment	Condition
CP-User data	RP-DATA

Table 11.1.1.3.3-3: Void

Table 11.1.1.3.3-4: Void

Table 11.1.1.3.3-5: Message UPLINK NAS TRANSPORT (step 4, Table 11.1.1.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.1.3.3-6: Void

Table 11.1.1.3.3-7: Message UPLINK NAS TRANSPORT (step 5, Table 11.1.1.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.1.3.3-8: Message CP-DATA (step 5, Table 11.1.1.3.2-1)

Information Element	Value/remark	Comment	Condition
CP-User data	RP-ACK

Table 11.1.1.3.3-9: Void

Table 11.1.1.3.3-10: Void

Table 11.1.1.3.3-11: Message DOWNLINK NAS TRANSPORT (step 6, Table 11.1.1.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.1.3.3-12: Void

11.1.2 MT-SMS over SGs / Active mode

11.1.2.1 Test Purpose (TP)

(1)

with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode }

ensure that {
when { UE receives a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message }

then { UE sends a CP-ACK encapsulated in an Uplink NAS transport message followed by a CP-DATA containing an RP-ACK RPDU encapsulated in an Uplink NAS transport message}

}

11.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clauses 5.6.3.1, 5.6.3.3, and 9.9.3.22.

[TS 24.301, clause 5.6.3.1]

[TS 24.301, clause 5.6.3.3]

[TS 24.301, clause 9.9.3.22]

This information element is used to encapsulate the SMS messages transferred between the UE and the network.The NAS message container information element is coded as shown in figure 9.9.3.22.1 and table 9.9.3.22.1.

The NAS message container is a type 4 information element with a minimum length of 4 octets and a maximum length of 253 octets.

8	7	6	5	4	3	2	1
NAS message container IEI								octet 1
Length of NAS message container contents								octet 2
								octet 3
NAS message container contents
								octet n

Figure 9.9.3.22.1: NAS message container information element

Table 9.9.3.22.1: NAS message container information element

NAS message container contents (octet 3 to octet n)

This IE can contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in subclause 7.2 in 3GPP TS 24.011 [13A].

11.1.2.3 Test description

11.1.2.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18].

– Cell A belongs TAI-1.

– Cell A is set to the ”Serving cell”.

UE:

– The UE does not have any stored SMS message.

Preamble:

– UE is in state Generic RB Established (state 3) on Cell A according to [18].

11.1.2.3.2 Test procedure sequence

Table 11.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a CP-DATA containing an RP-DATA RPDU (SMS DELIVER TPDU) encapsulated in a Downlink NAS transport message to the UE.	<–	DOWNLINK NAS TRANSPORT	–	–
2	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	1	P
3	Check: Does the UE transmit a CP-DATA containing an RP-ACK RPDU encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	1	P
4	The SS transmits a CP-ACK encapsulated in a Downlink NAS transport message to the UE.	<–	DOWNLINK NAS TRANSPORT	–	–

11.1.2.3.3 Specific message contents

Table 11.1.2.3.3-1: Message DOWNLINK NAS TRANSPORT (step 1, Table 11.1.2.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.2.3.3-2: Message CP-DATA (step 1, Table 11.1.2.3.2-1)

Information Element	Value/remark	Comment	Condition
CP-User data	RP-DATA

Table 11.1.2.3.3-3: Void

Table 11.1.2.3.3-4: Void

Table 11.1.2.3.3-5: Message UPLINK NAS TRANSPORT (step 2, Table 11.1.2.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.2.3.3-6: Void

Table 11.1.2.3.3-7: Message UPLINK NAS TRANSPORT (step 3, Table 11.1.2.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.2.3.3-8: Message CP-DATA (step 3, Table 11.1.2.3.2-1)

Information Element	Value/remark	Comment	Condition
CP-User data	RP-ACK

Table 11.1.2.3.3-9: Void

Table 11.1.2.3.3-10: Void

Table 11.1.2.3.3-12: Message DOWNLINK NAS TRANSPORT (step 4, Table 11.1.2.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.2.3.3-12: Void

11.1.3 MO-SMS over SGs / Idle mode

11.1.3.1 Test Purpose (TP)

(1)

with { UE is IMSI attached for non-EPS services and in EMM-IDLE mode }

ensure that {
when { a MO SMS is initiated at the UE }

then { UE sends an SERVICE REQUEST message followed by a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }

}

(2)

with { UE is IMSI attached for non-EPS services and UE has sent an SERVICE REQUEST message triggered by MO SMS followed by a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }

ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message }

then { UE sends a CP-ACK encapsulated in an Uplink NAS Transport message }

}

11.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clauses 5.6.3.1, 5.6.3.2 and 9.9.3.22., TS 23.401 clause 5.3.4.1.

[TS 24.301, clause 5.6.3.1]

[TS 24.301, clause 5.6.3.2]

Upon request from the SMS entity to send an SMS message, the EMM entity in the UE initiates the procedure by sending an UPLINK NAS TRANSPORT message including the SMS message in the NAS message container IE.

[TS 24.301, clause 9.9.3.22]

The NAS message container is a type 4 information element with a minimum length of 4 octets and a maximum length of 253 octets.

8	7	6	5	4	3	2	1
NAS message container IEI								octet 1
Length of NAS message container contents								octet 2
								octet 3
NAS message container contents
								octet n

Figure 9.9.3.22.1: NAS message container information element

Table 9.9.3.22.1: NAS message container information element

NAS message container contents (octet 3 to octet n)

This IE can contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in subclause 7.2 in 3GPP TS 24.011 [13A].

…

[TS 23.401, clause 5.3.4.1]

1. The UE sends NAS message Service Request towards the MME encapsulated in an RRC message to the eNodeB. The RRC message(s) that can be used to carry the S-TMSI and this NAS message are described in TS 36.300 [5].

2. The eNodeB forwards NAS message to MME. NAS message is encapsulated in an S1-AP: Initial UE Message (NAS message, TAI+ECGI of the serving cell, S-TMSI, CSG ID, CSG access Mode). Details of this step are described in TS 36.300 [5]. If the MME can’t handle the Service Request it will reject it. CSG ID is provided if the UE sends the Service Request message via a CSG cell or a hybrid cell. CSG access mode is provided if the UE sends the Service Request message via a hybrid cell. If the CSG access mode is not provided but the CSG ID is provided, the MME shall consider the cell as a CSG cell.

If a CSG ID is indicated and CSG access mode is not provided, and there is no subscription data for this CSG ID or the CSG subscription is expired, the MME rejects the Service Request with an appropriate cause. The UE shall remove the CSG ID of the cell where the UE has initiated the service request procedure from the Allowed CSG list, if present.

For UEs with emergency EPS bearers, i.e. at least one EPS bearer has an ARP values reserved for emergency services, if CSG access restrictions do not allow the UE to get normal services the MME shall deactivate all non-emergency bearers and accept the Service Request.

3. NAS authentication/security procedures as defined in clause 5.3.10 on "Security function" may be performed.

4. The MME sends S1-AP Initial Context Setup Request (Serving GW address, S1-TEID(s) (UL), EPS Bearer QoS(s), Security Context, MME Signalling Connection Id, Handover Restriction List, CSG Membership Indication) message to the eNodeB. This step activates the radio and S1 bearers for all the active EPS Bearers. The eNodeB stores the Security Context, MME Signalling Connection Id, EPS Bearer QoS(s) and S1-TEID(s) in the UE RAN context. The step is described in detail in TS 36.300 [5]. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions".

The MME shall only request to establish Emergency EPS Bearer if the UE is not allowed to access the cell where the UE initiated the service request procedure due to CSG access restriction.

If the Service Request is performed via a hybrid cell, CSG Membership Indication indicating whether the UE is a CSG member shall be included in the S1-AP message from the MME to the RAN. Based on this information the RAN can perform differentiated treatment for CSG and non-CSG members.

5. The eNodeB performs the radio bearer establishment procedure. The user plane security is established at this step, which is described in detail in TS 36.300 [5]. When the user plane radio bearers are setup. EPS bearer state synchronization is performed between the UE and the network, i.e. the UE shall locally remove any EPS bearer for which no radio bearers are setup and, if the radio bearer for a default EPS bearer is not established, the UE shall locally deactivate all EPS bearers associated to that default EPS bearer.

…

11.1.3.3 Test description

11.1.3.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18].

– Cell A belongs TAI-1.

– Cell A is set to the ”Serving cell”.

UE:

– The UE does not have any stored SMS message.

Preamble:

– UE is in state Registered, Idle Mode (state 2) on Cell A according to [18].

11.1.3.3.2 Test procedure sequence

Table 11.1.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Sending of a 160 character MO SMS is initiated at the UE via MMI or AT command	–	–	–	–
2	Check: Does the UE transmit an SERVICE REQUEST message?	–>	SERVICE REQUEST	1	P
3	Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	1	P
4	The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message.	<–	DOWNLINK NAS TRANSPORT	–	–
5	The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in an Downlink NAS transport message	<–	DOWNLINK NAS TRANSPORT	–	–
6	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message?	–>	UPLINK NAS TRANSPORT	2	P

11.1.3.3.3 Specific message contents

Table 11.1.3.3.3-1: Message UPLINK NAS TRANSPORT (step 3, Table 11.1.3.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.3.3.3-2: Message CP-DATA (step 3, Table 11.1.3.3.2-1)

Information Element	Value/remark	Comment	Condition
CP-User data	RP-DATA

Table 11.1.3.3.3-3: Void

Table 11.1.3.3.3-4: Void

Table 11.1.3.3.3-5: Message DOWNLINK NAS TRANSPORT (step 4, Table 11.1.3.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.3.3.3-6: Void

Table 11.1.3.3.3-7: Message DOWNLINK NAS TRANSPORT (step 5, Table 11.1.3.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.3.3.3-8: Message CP-DATA (step 5, Table 11.1.3.3.2-1)

Information Element	Value/remark	Comment	Condition
CP-User data	RP-ACK

Table 11.1.3.3.3-9: Void

Table 11.1.3.3.3-10: Void

Table 11.1.3.3.3-11: Message UPLINK NAS TRANSPORT (step 6, Table 11.1.3.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table Void

11.1.4 MO-SMS over SGs / Active mode

11.1.4.1 Test Purpose (TP)

(1)

with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode }

ensure that {
when { a MO SMS is initiated at the UE }

then { UE sends a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }

}

(2)

with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode and UE has sent a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }

ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message }

then { UE sends a CP-ACK encapsulated in an Uplink NAS Transport message }

}

11.1.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clauses 5.6.3.1, 5.6.3.2 and 9.9.3.22, and TS 23.401, clause 5.3.4.1.

[TS 24.301, clause 5.6.3.1]

[TS 24.301, clause 5.6.3.2]

[TS 24.301, clause 9.9.3.22]

This information element is used to encapsulate the SMS messages transferred between the UE and the network.The NAS message container information element is coded as shown in Table 9.9.3.22.1 and 9.9.3.22.2.

The NAS message container is a type 4 information element with a minimum length of 4 octets and a maximum length of 253 octets.

Table 9.9.3.22.1: NAS message container information element

8	7	6	5	4	3	2	1
NAS message container IEI								octet 1
Length of NAS message container contents								octet 2
								octet 3
NAS message container contents
								octet n

Table 9.9.3.22.2: NAS message container information element

NAS message container contents (octet 3 to octet n)

This IE can contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in subclause 7.2 in 3GPP TS 24.011 [13A].

…

[TS 23.401, clause 5.3.4]

2. The eNodeB forwards NAS message to MME. NAS message is encapsulated in an S1-AP: Initial UE Message (NAS message, TAI+ECGI of the serving cell, S-TMSI, CSG ID, CSG access Mode). Details of this step are described in TS 36.300 [5]. If the MME can’t handle the Service Request it will reject it. CSG ID is provided if the UE attaches via a closed or hybrid mode CSG cell. CSG access mode is provided if the UE sends the Service Request message via a hybrid mode CSG cell. If the CSG access mode is not provided but the CSG ID is provided, the MME shall consider the CSG cell as a closed mode CSG cell.

If a CSG ID is indicated and CSG access mode is "closed" or CSG access mode is not provided, and there is no subscription data for this CSG ID or the CSG subscription is expired, the MME rejects the Service Request with an appropriate cause. The UE shall remove the CSG ID of the cell where the UE has initiated the service request procedure from the Allowed CSG list.

3. NAS authentication procedures may be performed.

4. The MME sends S1-AP Initial Context Setup Request (Serving GW address, S1-TEID(s) (UL), EPS Bearer QoS(s), Security Context, MME Signalling Connection Id, Handover Restriction List) message to the eNodeB. This step activates the radio and S1 bearers for all the active EPS Bearers. The eNodeB stores the Security Context, MME Signalling Connection Id, EPS Bearer QoS(s) and S1-TEID(s) in the UE RAN context. The step is described in detail in TS 36.300 [5]. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions".

5. The eNodeB performs the radio bearer establishment procedure. The user plane security is established at this step, which is described in detail in TS 36.300 [5]. When the user plane radio bearers are setup the Service Request is completed and EPS bearer state is synchronized between the UE and the network, i.e. the UE should remove the EPS bearer for which no radio bearers are setup.

…

11.1.4.3 Test description

11.1.4.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18].

– Cell A belongs TAI-1.

– Cell A is set to the ”Serving cell”.

UE:

– The UE does not have any stored SMS message.

Preamble:

– UE is in state Generic RB Established (state 3) on Cell A according to [18].

11.1.4.3.2 Test procedure sequence

Table 11.1.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Sending of a 160 character MO SMS is initiated at the UE via MMI or AT command	–	–	–	–
2	Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	1	P
3	The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message.	<–	DOWNLINK NAS TRANSPORT	–	–
4	The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in an Downlink NAS transport message	<–	DOWNLINK NAS TRANSPORT	–	–
5	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message?	–>	UPLINK NAS TRANSPORT	2	P

11.1.4.3.3 Specific message contents

Table 11.1.4.3.3-1: Message UPLINK NAS TRANSPORT (step 2, Table 11.1.4.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.4.3.3-2: Message CP-DATA (step 2, Table 11.1.4.3.2-1)

Information Element	Value/remark	Comment	Condition
CP-User data	RP-DATA

Table 11.1.4.3.3-3: Void

Table 11.1.4.3.3-4: Void

Table 11.1.4.3.3-5: Message DOWNLINK NAS TRANSPORT (step 3, Table 11.1.4.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.4.3.3-6: Void

Table 11.1.4.3.3-7: Message DOWNLINK NAS TRANSPORT (step 4, Table 11.1.4.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.4.3.3-8: Message CP-DATA (step 4, Table 11.1.4.3.2-1)

Information Element	Value/remark	Comment	Condition
CP-User data	RP-ACK

Table 11.1.4.3.3-9: Void

Table 11.1.4.3.3-10: Void

Table 11.1.4.3.3-11: Message UPLINK NAS TRANSPORT (step 5, Table 11.1.4.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.4.3.3-12: Void

11.1.5 Multiple MO-SMS over SGs / Idle mode

11.1.5.1 Test Purpose (TP)

(1)

with { UE is IMSI attached for non-EPS services and in EMM-IDLE mode }

ensure that {
when { a MO SMS is initiated at the UE }

then { UE sends an SERVICE REQUEST message followed by a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }

}

(2)

ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU (SMS SUBMIT REPORT TPDU) encapsulated in a Downlink NAS transport message and has another MO SMS to send }

then { UE does not send a final CP-ACK before it sends a CP-DATA containing the successive RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS Transport message }

}

(3)

with { UE is IMSI attached for non-EPS services and UE has sent an SERVICE REQUEST message triggered by MO SMS followed by a CP-DATA containing an RP-DATA RPDU encapsulated in an Uplink NAS transport message }

ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU (SMS SUBMIT REPORT TPDU) encapsulated in a Downlink NAS transport message and does not have any further MO SMS to send }

then { UE sends a CP-ACK encapsulated in an Uplink NAS Transport message }

}

11.1.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clauses 5.6.3.1, 5.6.3.2 and 9.9.3.22, TS 23.401 clause 5.3.4.1 and TS 24.011 clause 5.4.

[TS 24.301, clause 5.6.3.1]

[TS 24.301, clause 5.6.3.2]

[TS 24.301, clause 9.9.3.22]

The NAS message container is a type 4 information element with a minimum length of 4 octets and a maximum length of 253 octets.

8	7	6	5	4	3	2	1
NAS message container IEI								octet 1
Length of NAS message container contents								octet 2
								octet 3
NAS message container contents
								octet n

Figure 9.9.3.22.1: NAS message container information element

Table 9.9.3.22.1: NAS message container information element

NAS message container contents (octet 3 to octet n)

This IE can contain an SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in subclause 7.2 in 3GPP TS 24.011 [13A].

[TS 23.401, clause 5.3.4.1]

3. NAS authentication/security procedures as defined in clause 5.3.10 on "Security function" may be performed.

The MME shall only request to establish Emergency EPS Bearer if the UE is not allowed to access the cell where the UE initiated the service request procedure due to CSG access restriction.

[TS 24.011, clause 5.4]

In the case of a SMS transfer via the PS domain, when the MS chooses to use the same PS signalling connection (in Iu mode and in S1 mode if packet-switched service is used); or in the case of a SMS transfer via the PS domain in A/Gb mode; or in the case of SMS transfer through the EPS, then:

the MS shall transmit the CP-DATA for the successive RPDU and shall not transmit the final CP‑ACK for the current SMS (i.e. the one that acknowledges the CP‑DATA that carried the RP‑ACK);

‑ the Transaction Identifier used for the successive RPDU shall be different to that used for the current RPDU; and

‑ the MS shall not transmit the CP-DATA for the successive RPDU before the final CP‑DATA (i.e. the one that carried the RP‑ACK) has been received.

NOTE: When an MS sends successive memory available notifications and/or mobile originated short messages on different RR connections (in A/Gb mode) or signalling connections (in Iu mode and S1 mode), the MS is strongly recommended to use different Transaction Identifiers for the old and new MM connections.

11.1.5.3 Test description

11.1.5.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18].

– Cell A belongs TAI-1.

– Cell A is set to the ”Serving cell”.

UE:

– The UE does not have any stored SMS message.

Preamble:

– UE is in state Registered, Idle Mode (state 2) on Cell A according to [18].

11.1.5.3.2 Test procedure sequence

Table 11.1.5.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Sending of 3 MO SMS as multiple SMS is initiated at the UE via MMI or AT command	–	–	–	–
2	Check: Does the UE transmit a SERVICE REQUEST message?	–>	SERVICE REQUEST	1	P
3	Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	1	P
4	The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message.	<–	DOWNLINK NAS TRANSPORT	–	–
5	The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message	<–	DOWNLINK NAS TRANSPORT	–	–
6	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message before the CP-DATA in step 7 is transmitted?	–>	UPLINK NAS TRANSPORT	2	F
7	Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	2	P
8	The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message.	<–	DOWNLINK NAS TRANSPORT	–	–
9	The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message	<–	DOWNLINK NAS TRANSPORT	–	–
10	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message before the CP-DATA in step 11 is transmitted?	–>	UPLINK NAS TRANSPORT	2	F
11	Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	2	P
12	The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message.	<–	DOWNLINK NAS TRANSPORT	–	–
13	The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message	<–	DOWNLINK NAS TRANSPORT	–	–
14	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message?	–>	UPLINK NAS TRANSPORT	3	P

11.1.5.3.3 Specific message contents

Table 11.1.5.3.3-1: Message UPLINK NAS TRANSPORT (step 3, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.5.3.3-2: Message CP-DATA (step 3, Table 11.1.5.3.2-1)

Information Element	Value/remark	Comment	Condition
Transaction identifier	TI used in steps 3, 4 and 5 shall be x.
CP-User data	RP-DATA

Table 11.1.5.3.3-3: Message DOWNLINK NAS TRANSPORT (step 4, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.5.3.3-4: Message DOWNLINK NAS TRANSPORT (step 5, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.5.3.3-5: Message UPLINK NAS TRANSPORT (step 7, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.5.3.3-6: Message CP-DATA (step 7, Table 11.1.5.3.2-1)

Information Element	Value/remark	Comment	Condition
Transaction identifier	TI used in steps 7, 8 and 9 shall be y, with y <> x (see step 3).
CP-User data	RP-DATA

Table 11.1.5.3.3-7: Message DOWNLINK NAS TRANSPORT (step 8, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.5.3.3-8: Message DOWNLINK NAS TRANSPORT (step 9, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.5.3.3-9: Message UPLINK NAS TRANSPORT (step 11, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.5.3.3-10: Message CP-DATA (step 11, Table 11.1.5.3.2-1)

Information Element	Value/remark	Comment	Condition
Transaction identifier	TI used in steps 11, 12, 13 and 14 shall be z, with z <> y (see step 7).
CP-User data	RP-DATA

Table 11.1.5.3.3-11: Message DOWNLINK NAS TRANSPORT (step 12, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.5.3.3-12: Message DOWNLINK NAS TRANSPORT (step 13, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.5.3.3-13: Message UPLINK NAS TRANSPORT (step 14, Table 11.1.5.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

11.1.6 Multiple MO-SMS over SGs / Active mode

11.1.6.1 Test Purpose (TP)

(1)

with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode }

ensure that {
when { a MO SMS is initiated at the UE }

then { UE sends a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }

}

(2)

with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode and UE has sent a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }

ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message and has another MO SMS to send }

then { UE does not send a final CP-ACK before it sends a CP-DATA containing the successive RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS Transport message }

}

(3)

with { UE is IMSI attached for non-EPS services and in EMM-CONNECTED mode and UE has sent a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message }

ensure that {
when { UE receives a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message and does not have any further MO SMS to send }

then { UE sends a CP-ACK encapsulated in an Uplink NAS Transport message }

}

11.1.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301, clauses 5.6.3.1, 5.6.3.2 and 9.9.3.22, and TS 24.011, clause 5.4.

[TS 24.301, clause 5.6.3.1]

[TS 24.301, clause 5.6.3.2]

[TS 24.011, clause 5.4]

– the MS shall transmit the CP-DATA for the successive RPDU and shall not transmit the final CP‑ACK for the current SMS (i.e. the one that acknowledges the CP‑DATA that carried the RP‑ACK);

– the Transaction Identifier used for the successive RPDU shall be different to that used for the current RPDU; and

– the MS shall not transmit the CP-DATA for the successive RPDU before the final CP‑DATA (i.e. the one that carried the RP‑ACK) has been received.

11.1.6.3 Test description

11.1.6.3.1 Pre-test conditions

System Simulator:

– Cell A is configured according to Table 6.3.2.2-1 in [18].

– Cell A belongs TAI-1.

– Cell A is set to the ”Serving cell”.

UE:

– The UE does not have any stored SMS message.

Preamble:

– UE is in state Generic RB Established (state 3) on Cell A according to [18].

11.1.6.3.2 Test procedure sequence

Table 11.1.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Sending of 3 MO SMS as multiple SMS is initiated at the UE via MMI or AT command	–	–	–	–
2	Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	1	P
3	The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message.	<–	DOWNLINK NAS TRANSPORT	–	–
4	The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message	<–	DOWNLINK NAS TRANSPORT	–	–
5	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message before the CP-DATA in step 6 is transmitted?	–>	UPLINK NAS TRANSPORT	2	F
6	Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	2	P
7	The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message.	<–	DOWNLINK NAS TRANSPORT	–	–
8	The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message	<–	DOWNLINK NAS TRANSPORT	–	–
9	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message before the CP-DATA in step 10 is transmitted?	–>	UPLINK NAS TRANSPORT	2	F
10	Check: Does the UE transmit a CP-DATA containing an RP-DATA RPDU (SMS SUBMIT TPDU) encapsulated in an Uplink NAS transport message?	–>	UPLINK NAS TRANSPORT	2	P
11	The SS transmits a CP-ACK encapsulated in a Downlink NAS Transport message.	<–	DOWNLINK NAS TRANSPORT	–	–
12	The SS transmits a CP-DATA containing an RP-ACK RPDU encapsulated in a Downlink NAS transport message	<–	DOWNLINK NAS TRANSPORT	–	–
13	Check: Does the UE transmit a CP-ACK encapsulated in an Uplink NAS Transport message?	–>	UPLINK NAS TRANSPORT	3	P

11.1.6.3.3 Specific message contents

Table 11.1.6.3.3-1: Message UPLINK NAS TRANSPORT (step 2, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.6.3.3-2: Message CP-DATA (step 2, Table 11.1.6.3.2-1)

Information Element	Value/remark	Comment	Condition
Transaction identifier	TI used in steps 2, 3 and 4 shall be x.
CP-User data	RP-DATA

Table 11.1.6.3.3-3: Message DOWNLINK NAS TRANSPORT (step 3, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.6.3.3-4: Message DOWNLINK NAS TRANSPORT (step 4, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.6.3.3-5: Message UPLINK NAS TRANSPORT (step 6, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.6.3.3-6: Message CP-DATA (step 6, Table 11.1.6.3.2-1)

Information Element	Value/remark	Comment	Condition
Transaction identifier	TI used in steps 6, 7 and 8 shall be y, with y <> x (see step 2).
CP-User data	RP-DATA

Table 11.1.6.3.3-7: Message DOWNLINK NAS TRANSPORT (step 7, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.6.3.3-8: Message DOWNLINK NAS TRANSPORT (step 8, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.6.3.3-9: Message UPLINK NAS TRANSPORT (step 10, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.6.3.3-10: Message CP-DATA (step 10, Table 11.1.6.3.2-1)

Information Element	Value/remark	Comment	Condition
Transaction identifier	TI used in steps 10, 11, 12 and 13 shall be z, with z <> y (see step 6).
CP-User data	RP-DATA

Table 11.1.6.3.3-11: Message DOWNLINK NAS TRANSPORT (step 11, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK

Table 11.1.6.3.3-12: Message DOWNLINK NAS TRANSPORT (step 12, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-12A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-DATA

Table 11.1.6.3.3-13: Message UPLINK NAS TRANSPORT (step 13, Table 11.1.6.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27A
Information Element	Value/remark	Comment	Condition
NAS message container	CP-ACK