22.6 ESM-CIoT

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

22.6.1 NB-IoT / UE routing of uplinks packets / User Plane / UE requested PDN disconnect procedure accepted by the network

22.6.1.1.1 Test Purpose (TP)

(1)

Void

(2)

with { the UE is in BEARER CONTEXT ACTIVE STATE and in EMM-CONNECTED mode with a default EPS bearer }

ensure that {

when { the UE has an IP packet for transmission AND no packet filter is configured for the default EPS bearer }

then { the UE transmits the IP packet in uplink on the default EPS bearer }

}

(3)

with { the UE is in BEARER CONTEXT ACTIVE STATE and in EMM-CONNECTED mode with a default EPS bearer }

ensure that {

when { the UE has an IP packet for transmission where the IP header only satisfies a packet filter configured in the UL TFT for the default EPS bearer }

then { the UE transmits the IP packet in uplink on the default EPS bearer }

}

(4)

with { the UE is in BEARER CONTEXT ACTIVE STATE and in EMM-CONNECTED mode with a default EPS bearer }

ensure that {

when { the UE has an IP packet for transmission where the IP header does not satisfy any of the configured packet filters in the UL TFT configured for the default EPS bearers }

then { the UE discards the IP packet }

}

(5)

with { UE is in BEARER CONTEXT ACTIVE STATE }

ensure that {

when { UE is triggered to disconnect from a PDN }

then { UE sends a PDN DISCONNECT REQUEST message including the default EPS bearer identity associated with this PDN }

}

(6)

with { UE is in PROCEDURE TRANSACTION PENDING state }

ensure that {

when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message with any valid ESM cause }

then { UE deactivates the default EPS bearer context for this PDN connection between the UE and the SS }

}

22.6.1.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 23.060, clause 15.3.2.0, TS 24.008, clause 10.5.6.12 and TS 24.301, clauses 6.4.4.2, 6.5.2.2 and 6.5.2.4.

[TS 23.060, clause 15.3.2.0]

Each valid downlink- and uplink-packet filter contains a unique identifier within a given TFT, an evaluation precedence index that is unique among all packet filters for one PDP address and APN pair, and at least one of the following attributes:

– Remote Address and Subnet Mask.

– Protocol Number (IPv4) / Next Header (IPv6).

– Local Address and Mask.

– Local Port Range.

– Remote Port Range.

– IPSec Security Parameter Index (SPI).

– Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask.

– Flow Label (IPv6).

In the list of attributes above ‘Remote’ refers to the external network entity, and ‘Local’ to the MS.

Some of the above-listed attributes may coexist in a packet filter while others mutually exclude each other. In table 12 below, the possible combinations are shown. Only those attributes marked with an "X" may be specified for a single packet filter. All marked attributes may be specified, but at least one shall be specified.

If the parameters of the header of a received PDP PDU match all specified attribute values in a packet filter, then it is considered that a match is found for this packet filter. In this case, the evaluation procedure is aborted. Other packet filters in increasing order of their evaluation precedence index are evaluated until such match is found.

There may be potential conflicts if attribute values are combined in such a way that the defined filter can never achieve a match to a valid IP packet header. However, the determination of such conflicts is outside the scope of GPRS standardization.

Table 12: Valid Packet Filter Attribute Combinations

	Valid combination types
Packet filter attribute	I	II	III
Remote Address and Subnet Mask	X	X	X
Protocol Number (IPv4) / Next Header (IPv6)	X	X
Local Address and Mask	X	X	X
Local Port Range	X
Remote Port Range	X
IPSec SPI		X
TOS (IPv4) / Traffic Class (IPv6) and Mask	X	X	X
Flow Label (IPv6)			X

[TS 24.008, clause 10.5.6.12]

The purpose of the traffic flow template information element is to specify the TFT parameters and operations for a PDP context. In addition, this information element may be used to transfer extra parameters to the network (e.g. the Authorization Token; see 3GPP TS 24.229 [95]). The TFT may contain packet filters for the downlink direction, the uplink direction or packet filters that are applicable to both directions. The packet filters determine the traffic mapping to PDP contexts. The downlink packet filters shall be used by the network and the uplink packet filters shall be used by the MS. A packet filter that is applicable to both directions shall be used by the network as a downlink packet filter and by the MS as an uplink packet filter.

The traffic flow template is a type 4 information element with a minimum length of 3 octets. The maximum length for the IE is 257 octets.

NOTE 1: The IE length restriction is due to the maximum length that can be encoded in a single length octet.

NOTE 2: A maximum size IPv4 packet filter can be 32 bytes. Therefore, 7 maximum size IPv4 type packet filters, plus the last packet filter which can contain max 30 octets can fit into one TFT IE, i.e. if needed not all packet filter components can be defined into one message. A maximum size IPv6 packet filter can be 60 bytes. Therefore, only 4 maximum size IPv6 packet filters can fit into one TFT IE. However, using "Add packet filters to existing TFT", it’s possible to create a TFT data structure including 16 maximum size IPv4 or IPv6 filters.

The traffic flow template information element is coded as shown in figure 10.5.144/3GPP TS 24.008 and table 10.5.162/3GPP TS 24.008.

NOTE 3: The 3GPP TS 24.301 [120] reuses the traffic flow template information element for the purpose of the traffic aggregate description, where the use of individual TFT parameters, e.g. the packet filter identifier in the parameter list, can differ from this specification.

8	7	6	5		4		3	2	1
Traffic flow template IEI										Octet 1
Length of traffic flow template IE										Octet 2
TFT operation code				E bit		Number of packet filters				Octet 3
Packet filter list										Octet 4 Octet z
Parameters list										Octet z+1 Octet v

Figure 10.5.144/3GPP TS 24.008: Traffic flow template information element

8	7	6	5	4	3	2	1
0	0	0	0	Packet filter identifier 1				Octet 4
Spare
0	0	0	0	Packet filter identifier 2				Octet 5
Spare
…
0	0	0	0	Packet filter identifier N				Octet N+3
Spare

Figure 10.5.144a/3GPP TS 24.008: Packet filter list when the TFT operation is "delete packet filters from existing TFT" (z=N+3)

8	7	6	5	4	3	2	1
0	0	Packet filter direction 1		Packet filter identifier 1				Octet 4
Spare
Packet filter evaluation precedence 1								Octet 5
Length of Packet filter contents 1								Octet 6
Packet filter contents 1								Octet 7 Octet m
0	0	Packet filter direction 2		Packet filter identifier 2				Octet m+1
Spare
Packet filter evaluation precedence 2								Octet m+2
Length of Packet filter contents 2								Octet m+3
Packet filter contents 2								Octet m+4 Octet n
…								Octet n+1 Octet y
0	0	Packet filter direction N		Packet filter identifier N				Octet y+1
Spare
Packet filter evaluation precedence N								Octet y+2
Length of Packet filter contents N								Octet y+3
Packet filter contents N								Octet y+4 Octet z

Figure 10.5.144b/3GPP TS 24.008: Packet filter list when the TFT operation is "create new TFT", or "add packet filters to existing TFT" or "replace packet filters in existing TFT"

8	7	6	5	4	3	2	1
Parameter identifier 1								Octet z+1
Length of Parameter contents 1								Octet z+2
Parameter contents 1								Octet z+3 Octet k
Parameter identifier 2								Octet k+1
Length of Parameter contents 2								Octet k+2
Parameter contents 2								Octet k+3 Octet p
…								Octet p+1 Octet q
Parameter identifier N								Octet q+1
Length of Parameter contents N								Octet q+2
Parameter contents N								Octet q+3 Octet v

Figure 10.5.144c/3GPP TS 24.008: Parameters list

Table 10.5.162/3GPP TS 24.008: Traffic flow template information element

TFT operation code (octet 3)
Bits
8 7 6

0 0 0 Spare
0 0 1 Create new TFT

0 1 0 Delete existing TFT

0 1 1 Add packet filters to existing TFT

1 0 0 Replace packet filters in existing TFT

1 0 1 Delete packet filters from existing TFT

1 1 0 No TFT operation

1 1 1 Reserved

The TFT operation code "No TFT operation" shall be used if a parameters list is included but no packet filter list is included in the traffic flow template information element.

E bit (bit 5 of octet 3)

The E bit indicates if a parameters list is included in the TFT IE and it is encoded as follows:

0 parameters list is not included

1 parameters list is included

Number of packet filters (octet 3)

The number of packet filters contains the binary coding for the number of packet filters in the packet filter list. The number of packet filters field is encoded in bits 4 through 1 of octet 3 where bit 4 is the most significant and bit 1 is the least significant bit. For the "delete existing TFT" operation and for the "no TFT operation", the number of packet filters shall be coded as 0. For all other operations, the number of packet filters shall be greater than 0 and less than or equal to 15.

Packet filter list (octets 4 to z)

The packet filter list contains a variable number of packet filters. For the "delete existing TFT" operation and the "no TFT operation", the packet filter list shall be empty.

For the "delete packet filters from existing TFT" operation, the packet filter list shall contain a variable number of packet filter identifiers. This number shall be derived from the coding of the number of packet filters field in octet 3.

For the "create new TFT", "add packet filters to existing TFT" and "replace packet filters in existing TFT" operations, the packet filter list shall contain a variable number of packet filters. This number shall be derived from the coding of the number of packet filters field in octet 3.

Each packet filter is of variable length and consists of

– a packet filter identifier and direction (1 octet);
– a packet filter evaluation precedence (1 octet);

– the length of the packet filter contents (1 octet); and
– the packet filter contents itself (v octets).

The packet filter identifier field is used to identify each packet filter in a TFT. The least significant 4 bits are used.

The packet filter direction is used to indicate, in bits 5 and 6, for what traffic direction the filter applies:

00 – pre Rel-7 TFT filter
01 – downlink only
10 – uplink only
11 – bidirectional

Bits 8 through 7 are spare bits.

The packet filter evaluation precedence field is used to specify the precedence for the packet filter among all packet filters in all TFTs associated with this PDP address. Higher the value of the packet filter evaluation precedence field, lower the precedence of that packet filter is. The first bit in transmission order is the most significant bit.

The length of the packet filter contents field contains the binary coded representation of the length of the packet filter contents field of a packet filter. The first bit in transmission order is the most significant bit.

The packet filter contents field is of variable size and contains a variable number (at least one) of packet filter components. Each packet filter component shall be encoded as a sequence of a one octet packet filter component type identifier and a fixed length packet filter component value field. The packet filter component type identifier shall be transmitted first.

In each packet filter, there shall not be more than one occurrence of each packet filter component type. Among the "IPv4 remote address type" and "IPv6 remote address type" packet filter components, only one shall be present in one packet filter. Among the "single local port type" and "local port range type" packet filter components, only one shall be present in one packet filter. Among the "single remote port type" and "remote port range type" packet filter components, only one shall be present in one packet filter.

The term local refers to the MS and the term remote refers to an external network entity.

Packet filter component type identifier
Bits
8 7 6 5 4 3 2 1

0 0 0 1 0 0 0 0 IPv4 remote address type
0 0 0 1 0 0 0 1 IPv4 local address type
0 0 1 0 0 0 0 0 IPv6 remote address type
0 0 1 0 0 0 0 1 IPv6 remote address/prefix length type
0 0 1 0 0 0 1 1 IPv6 local address/prefix length type
0 0 1 1 0 0 0 0 Protocol identifier/Next header type
0 1 0 0 0 0 0 0 Single local port type
0 1 0 0 0 0 0 1 Local port range type
0 1 0 1 0 0 0 0 Single remote port type
0 1 0 1 0 0 0 1 Remote port range type
0 1 1 0 0 0 0 0 Security parameter index type
0 1 1 1 0 0 0 0 Type of service/Traffic class type
1 0 0 0 0 0 0 0 Flow label type

All other values are reserved.

The description and valid combinations of packet filter component type identifiers in a packet filter are defined in 3GPP TS 23.060 [74] subclause 15.3.2.

For "IPv4 remote address type", the packet filter component value field shall be encoded as a sequence of a four octet IPv4 address field and a four octet IPv4 address mask field. The IPv4 address field shall be transmitted first.

For "IPv4 local address type", the packet filter component value field shall be encoded as defined for "IPv4 remote address type".
Both the MS and network indication for support of the Local address in TFTs are required to use this packet filter component.

For "IPv6 remote address type", the packet filter component value field shall be encoded as a sequence of a sixteen octet IPv6 address field and a sixteen octet IPv6 address mask field. The IPv6 address field shall be transmitted first.

For "IPv6 remote address/prefix length type", the packet filter component value field shall be encoded as a sequence of a sixteen octet IPv6 address field and one octet prefix length field. The IPv6 address field shall be transmitted first.
This parameter shall be used, instead of IPv6 remote address type, when both the MS and network indication for support of the Local address in TFT are present.

For "IPv6 local address/prefix length type", the packet filter component value field shall be encoded as defined for "IPv6 remote address /prefix length".

Both the MS and network indication for support of the Local address in TFTs are required to use this packet filter component.

NOTE: Local IP address and mask can be used when IPv6 prefix delegation is used (see 3GPP TS 23.060 [74] subclause 9.2.1.2).

For "Protocol identifier/Next header type", the packet filter component value field shall be encoded as one octet which specifies the IPv4 protocol identifier or IPv6 next header.

For "Single local port type" and "Single remote port type", the packet filter component value field shall be encoded as two octet which specifies a port number.

For "Local port range type" and "Remote port range type", the packet filter component value field shall be encoded as a sequence of a two octet port range low limit field and a two octet port range high limit field. The port range low limit field shall be transmitted first.

For "Security parameter index", the packet filter component value field shall be encoded as four octet which specifies the IPSec security parameter index.

For "Type of service/Traffic class type", the packet filter component value field shall be encoded as a sequence of a one octet Type-of-Service/Traffic Class field and a one octet Type-of-Service/Traffic Class mask field. The Type-of-Service/Traffic Class field shall be transmitted first.

For "Flow label type", the packet filter component value field shall be encoded as three octet which specifies the IPv6 flow label. The bits 8 through 5 of the first octet shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label.

Parameters list (octets z+1 to v)

The parameters list contains a variable number of parameters that may be transferred. If the parameters list is included, the E bit is set to 1; otherwise, the E bit is set to 0.

Each parameter included in the parameters list is of variable length and consists of:

– a parameter identifier (1 octet);
– the length of the parameter contents (1 octet); and
– the parameter contents itself (v octets).

The parameter identifier field is used to identify each parameter included in the parameters list and it contains the hexadecimal coding of the parameter identifier. Bit 8 of the parameter identifier field contains the most significant bit and bit 1 contains the least significant bit. In this version of the protocol, the following parameter identifiers are specified:

– 01H (Authorization Token);

– 02H (Flow Identifier); and
– 03H (Packet Filter Identifier).

If the parameters list contains a parameter identifier that is not supported by the receiving entity the corresponding parameter shall be discarded.

The length of parameter contents field contains the binary coded representation of the length of the parameter contents field. The first bit in transmission order is the most significant bit.

When the parameter identifier indicates Authorization Token, the parameter contents field contains an authorization token, as specified in 3GPP TS 29.207 [100]. The first octet is the most significant octet of the authorization token and the last octet is the least significant octet of the authorization token.

The parameters list shall be coded in a way that an Authorization Token (i.e. a parameter with identifier 01H) is always followed by one or more Flow Identifiers (i.e. one or more parameters with identifier 02H).

If the parameters list contains two or more consecutive Authorization Tokens without any Flow Identifiers in between, the receiver shall treat this as a semantical TFT error.

When the parameter identifier indicates Flow Identifier, the parameter contents field contains the binary representation of a flow identifier. The Flow Identifier consists of four octets. Octets 1 and 2 contains the Media Component number as specified in 3GPP TS 29.207 [100]. Bit 1 of octet 2 is the least significant bit, and bit 8 of octet 1 is the most significant bit. Octets 3 and 4 contains the IP flow number as specified in 3GPP TS 29.207 [100]. Bit 1 of octet 4 is the least significant bit, and bit 8 of octet 3 is the most significant bit.

When the parameter identifier indicates Packet Filter Identifier, the parameter contents field contains the binary representation of one or more packet filter identifiers. Each packet filter identifier is encoded in one octet, in the 4 least significant bits. This parameter is used by the MS and the network to identify one or more packet filters in a TFT when modifying the QoS of a PDP context without modifying the packet filter itself.

[TS 24.301, clause 6.5.2.2]

In order to request PDN disconnection from a PDN, the UE shall send a PDN DISCONNECT REQUEST message to the MME, start the timer T3492 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.2.2.1). The PDN DISCONNECT REQUEST message shall include the EPS bearer identity of the default bearer associated with the PDN to disconnect from as the linked EPS bearer identity in the PDN DISCONNECT REQUEST message.

[TS 24.301, clause 6.5.2.3]

…

Upon receipt of the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall stop the timer T3492 and enter the state PROCEDURE TRANSACTION INACTIVE. The behaviour of the UE is described in subclause 6.4.4.

[TS 24.301, clause 6.4.4.2]

If a NAS signalling connection exists when the MME initiates the EPS bearer context deactivation procedure, the MME shall initiate the EPS bearer context deactivation procedure by sending a DEACTIVATE EPS BEARER CONTEXT REQUEST message to the UE, start the timer T3495, and enter the state BEARER CONTEXT INACTIVE PENDING (see example in figure 6.4.4.2.1). The DEACTIVATE EPS BEARER CONTEXT REQUEST message contains an ESM cause typically indicating one of the following:

#8: operator determined barring;

#26: insufficient resources;

#36: regular deactivation;

#38: network failure;

#39: reactivation requested;

#112: APN restriction value incompatible with active EPS bearer context; or

#113: Multiple accesses to a PDN connection not allowed.

If the deactivation is triggered by a UE initiated bearer resource modification procedure or UE requested PDN disconnect procedure, the DEACTIVATE EPS BEARER CONTEXT REQUEST message shall contain the procedure transaction identity (PTI) value received by the MME in the BEARER RESOURCE MODIFICATION REQUEST or PDN DISCONNECT REQUEST respectively.

…

22.6.1.1.3 Test description

22.6.1.1.3.1 Pre-test conditions

System Simulator:

– NB-IoT Ncell 1, default parameter;

UE:

– None

Preamble:

– The UE is in state Switched OFF (State 1)

22.6.1.1.3.2 Test procedure sequence

Table 22.6.1.3.2-1: Packet filters

Packet filter components

Packet filter ID

UL TFT

Packet filter evaluation precedence

Protocol Number (IPv4) / Next Header (IPv6)

Remote address and Subnet mask

Single Local Port

(UE)

Local Port Range

(UE)

Single Remote Port

(NW)

Remote Port Range

(NW)

IPSec SPI range

Type of Service (IPv4) / Traffic Class (IPv6) and Mask

Flow Label (IPv6)

Comments

DRB1

(default bearer)

(UDP)

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

60001

–

60350:

60450

–

10101000, Mask=
11111100

–

UDP application identified by remote address, type of service/traffic class and specific local and remote port numbers

This is a valid Packet Filter Attribute Combination Type I according to TS 23.060, subclause 15.3.2.0.

DRB1

(default bearer)

(UDP)

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

–

60000:60100

–

60350

–

10101000, Mask=
11111100

–

UDP application identified by remote address, type of service/traffic class and range of local and remote port numbers. This is a valid Packet Filter Attribute Combination Type I according to TS 23.060, subclause 15.3.2.0.

DRB1

(default bearer)

50
IPSec (ESP)

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

–

0x0F80F0000

10100000, Mask=
11111100

–

IPSec session. Example from TS 23.060 clause 15.3.3.3

This is a valid Packet Filter Attribute Combination Type II according to TS 23.060, subclause 15.3.2.0.

DRB1

(default bearer)

–

IPv6:

2001:0ba0:: [ffff:ffff::]

–

10110000, Mask=
11111100

IPv6 Flow Label filter.

This is a valid Packet Filter Attribute Combination Type III according to TS 23.060, subclause 15.3.2.0.

DRB1

(default bearer)

255

–

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

–

Application identified by remote address.

This is a valid Packet Filter Attribute Combination Type I according to TS 23.060, subclause 15.3.2.0.

Table 22.6.1.3.2-2: Sub-test test parameters and test requirements

Sub-test Index	Test data (IP packet) Note 1	Expected DRB associated with the EPS bearer context for the matching packet filter	Packet Filter Attribute Combination under test	Packet Filter Component under test	Comment
1	IP packet#1	DRB1	Type I	Remote Address does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer) as no filters are activated.
2	IP packet#2	DRB1	Type I	Protocol identifier/Next header does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer) as no filters are activated.
3	IP packet#3	DRB1	Type I	Local port range does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer) as no filters are activated.
4	IP packet#4	None	Type I	Remote port range does not match	No packet filter matches. The IP packet is not returned ..
5	IP packet#5	DRB1	Type I	All Type I packet filter components match	The IP packet is only matching Packet Filter 1 and 2 in Table 22.6.1.3.2-1. The IP packet is returned on DRB1
6	IP packet#6	None	Type II	Remote Address does not match	No packet filter matches. The IP packet is not returned.
7	IP packet#7	None	Type II	Protocol identifier/Next header does not match	No packet filter matches. The IP packet is not returned.
8	IP packet#8	None	Type II	Security parameter index does not match	No packet filter matches. The IP packet is not returned.
9	IP packet#9	DRB1	Type II	All Type II packet filter components match	The IP packet is only matching Packet Filter 3 in Table 22.6.1.3.2-1. The IP packet is returned on DRB1.
10	IP packet#10	None	Type III	Remote Address does not match	No packet filter matches. The IP packet is not returned.
11	IP packet#11	None	Type III	Type of service/Traffic class does not match	No packet filter matches. The IP packet is not returned.
12	IP packet#12	DRB1	Type III	All Type III packet filter components match	The IP packet is only matching Packet Filter 4 in Table 22.6.1.3.2-1. The IP packet is returned on DRB1.
13	IP packet#13	DRB1	Type I	Remote Address match	IP packet is only matching Packet Filter 5 in Table 22.6.1.3.2-1. The IP packet is returned on DRB1.
14	IP packet#14	None	Type I	Remote Address does not match	No packet filter matches. The IP packet is not returned
Note 1: IP Packet details are specified in Tables 22.6.1.3.3-7 to 22.6.1.3.3-26 in clause 22.6.1.3.3. Note 2: IP packets for sub-test index 1 to 3 are sent by the SS while no TFT is assigned to the default EPS bearer (associated by DRB1). IP packets for sub-test index 4 and 14 are sent by the SS after adding a TFT to the default EPS bearer.

The test procedure in Table 22.6.1.3.2-3, steps 1- 14 is executed once for IPv4 case (sub test 1) and once for IPv6 case (sub test 2) dependent on UE capability as specified in Table 22.6.1.3.2-3.

Table 22.6.1.3.2-3: Test executions and test parameters

Sub test	Applicability	IPtyp
1	UE supporting IPv4	‘IPv4’
2	UE supporting IPv6	‘IPv6’
Note 1: For UEs supporting both IPv4 and IPv6 then both test execution 1 and 2 shall be performed.

Table 22.6.1.1.3.2-4: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS performs the generic procedure in subclause 8.1.5.2A in 36.508 to get UE in the Test Mode Activated (State 2A-NB) state with test loop mode B on Ncell1 establishing a default EPS bearer in accordance to Reference default EPS bearer context #1 (DRB1) as specified in subclause 6.6.1 in TS 36.508 [18].	–	–	–	–
2	The SS performs the generic procedure in subclause 8.1.5.2B in [18] to get UE in the Test Loopback Activated (State 2B-NB) with test loop mode B.	–	–	–	–
–	EXCEPTION: IF IPtype=’IPv4′ then test steps 3 to 4 are repeated for N = 1 to 3 using the IPv4 packet filters components in Table 22.6.1.3.2-1. IF IPtype=’IPv6′ then test steps 3 to 4 are repeated for N = 1 to 3 using the IPv6 packet filters components in Table 22.6.1.3.2-1.	–	–	–	–
–	Void	–	–	–	–
3	The SS transmits one IP Packet according to Table 22.6.1.3.2-2 for Sub-test index=N on DRB1	–	–	–	–
4	Check: Does UE send the IP Packet on the data radio bearer as specified by Table 22.6.1.3.2-2 for Sub-test index=N?	–	–	2	P
5	The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message to add TFT to the default EPS bearer. This message is included in a DLInformationTransfer message.	<–	MODIFY EPS BEARER CONTEXT REQUEST	–	–
6	UE transmits a MODIFY EPS BEARER CONTEXT ACCEPT message	–>	MODIFY EPS BEARER CONTEXT ACCEPT	–	–
–	EXCEPTION: IF IPtype=’IPv4′ then test steps 7 to 8 are repeated for N = 5, 9 and 13 using the IPv4 packet filters components in Table 22.6.1.3.2-1. IF IPtype=’IPv6′ then test steps 7 to 8 are repeated for N = 5, 9, 12 and 13 using the IPv6 packet filters components in Table 22.6.1.3.2-1.	–	–	–	–
7	The SS transmits one IP Packet according to Table 22.6.1.3.2-2 for Sub-test index= N on DRB1	–	–	–	–
8	Check: Does UE send the IP Packet on the data radio bearer as specified by Table 22.6.1.3.2-2 for Sub-test index= N ?	–	–	3	P
–	EXCEPTION: IF IPtype=’IPv4′ then test steps 9 to 10 are repeated for N = 4, 6-8 and 14 using the IPv4 packet filters components in Table 22.6.1.3.2-1. IF IPtype=’IPv6′ then test steps 9 to 10 are repeated for N = 4, 6-8, 10-11 and 14 using the IPv6 packet filters components in Table 22.6.1.3.2-1.	–	–	–	–
9	The SS transmits one IP Packet according to Table 22.6.1.3.2-2 for Sub-test index=14 on DRB1	–	–	–	–
10	Check: Does UE send an IP Packet on the data radio bearer?	–	–	4	F
11	The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode.	<–	RRC: DLInformationTransfer-NB TC: OPEN UE TEST LOOP	–	–
12	The UE transmits an OPEN UE TEST LOOP COMPLETE message.	–>	RRC: ULInformationTransfer-NB TC: OPEN UE TEST LOOP COMPLETE	–	–
13	The SS transmits an DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure.	<–	RRC: DLInformationTransfer-NB TC: DEACTIVATE TEST MODE	–	–
14	The UE transmits an DEACTIVATE TEST MODE COMPLETE message.	–>	RRC: ULInformationTransfer-NB TC: DEACTIVATE TEST MODE COMPLETE	–	–
–	EXCEPTION: If this is the first of two executions according to table 22.6.1.3.2-3, step 15 is performed, otherwise the test is continued from step 16.
15	The UE is switched OFF, see Note 1. The test is restarted from step 1.	–	–	–	–
–	EXCEPTION: Steps 16a1 to 16a15 describe behaviour that depends on UE configuration; the "lower case letter" identifies a step sequence that take place if the UE supports multiple DRBs in NB-IoT.	–	–	–	–
16a1	Void			–	–
16a2	Void			–	–
16a2A	Void			–	–
16a3	IF pc_NB_MultiDRB cause the UE to request connectivity to an additional PDN (see Note 3)	–	–	–	–
16a4	Void			–	–
16a5	Check: Does the UE transmit a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN?	–>	PDN CONNECTIVITY REQUEST	–	–
16a6	SS transmits a RRCConnectionReconfiguration-NB message to establish the default. This message includes the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message.	<–	RRC: RRCConnectionReconfiguration-NB ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST	–	–
16a7	The UE transmits an RRCConnectionReconfigurationComplete-NB message to confirm the establishment of default bearer,	–>	RRC: RRCConnectionReconfigurationComplete-NB	–	–
–	EXCEPTION: In parallel to the event described in step 16a8 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 [18] subclause 4.5A.1 takes place performing IP address allocation in the U-plane.	–	–	–	–
16a8	Check: Does the UE transmit an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS Bearer?	–>	ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT	–	–
16a9	Void			–	–
16a10	Cause the UE to request disconnection from the additional PDN (see Note 2)	–	–	–	–
16a11	Void			–	–
16a12	Check: Does the UE transmit a PDN DISCONNECT REQUEST message to disconnect from the additional PDN?	–>🡪	PDN DISCONNECT REQUEST	5	p
16a13	Void
16a14	The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message included in an RRCConnectionReconfiguration-NB message.	<–	DEACTIVATE EPS BEARER CONTEXT REQUEST	–	–
16a15	Check: Does the UE transmit a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.	–>	DEACTIVATE EPS BEARER CONTEXT ACCEPT	6	P
NOTE 1: This implies detaching of the UE, releasing of the RRC connection and resetting of the radio bearers at the SS side. NOTE 2: The request to disconnect from a PDN may be performed by MMI or AT command. NOTE 3: The request of connectivity to an additional PDN may be performed by MMI or AT command.

22.6.1.1.3.3 Specific message contents

Table 22.6.1.3.3-1: UECapabilityInformation (step 1, Table 22.6.1.3.2-3)

Derivation Path: 36.508 table 8.1.6.1-17
Information Element	Value/remark	Comment	Condition
PDN address
criticalExtensions CHOICE {
ueCapabilityInformation-r13 SEQUENCE {
ue-Capability-Container-r13 SEQUENCE {
multipleDRB-r13	supported		pc_NB_MultiDRB
	Not present		NOT pc_NB_MultiDRB
}
}
}

Table 22.6.1.3.3-2: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Test execution 2: step 1, Table 22.6.1.3.2-3)

Derivation Path: 36.508 table 4.7.3-6
Information Element		Value/remark		Comment	Condition
PDN address
Length of PDN address contents	9 octets
PDN type value	‘010’B		IPv6
PDN address information	IPv6 interface identifier		The SS provides a valid IPv6 interface identifier
ESM cause		IF "PDN type" IE in step 4 (preamble) is ‘IPv4v6’ THEN ‘00110011’B ELSE Not present		"PDN type IPv6 only allowed"

Table 22.6.1.3.3-3: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Test execution 1: step 1, Table 22.6.1.3.2-3)

Derivation Path: 36.508 table 4.7.3-6
Information Element		Value/remark		Comment	Condition
PDN address
Length of PDN address contents	5 octets
PDN type value	‘001’B		IPv4
PDN address information	IPv4 address		The SS provides a valid IPv4 address
ESM cause		IF "PDN type" IE in step 4 (preamble) is ‘IPv4v6’ THEN ‘00110010’B ELSE Not present		"PDN type IPv4 only allowed"

Table 22.6.1.3.3-4: Void

Table 22.6.1.3.3-5: Message MODIFY EPS BEARER CONTEXT REQUEST (step 5, Table 22.6.1.3.2-3)

Derivation path: 36.508 table 4.7.3-16 and table 4.6.1-3
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message	SS assigns the current default EPS bearer context.
Procedure transaction identity	0	"No procedure transaction identity assigned"
TFT
TFT operation code	“Create new TFT”
E bit	0
Packet filters (Note 1)	1,2,3,4,5	SS adds packet filters to the default EPS bearer context.
Note 1: This row refers to the packet filters defined in Table 22.6.1.3.2-1.

Table 22.6.1.3.3-6: Message MODIFY EPS BEARER CONTEXT ACCEPT (step 6, Table 22.6.1.3.2-3)

Derivation path: 36.508 table 4.7.3-14
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message	Same value as in MODIFY EPS BEARER CONTEXT REQUEST
Procedure transaction identity	0	"No procedure transaction identity assigned"

Table 22.6.1.3.3-7: IP packet#1 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#5, Table 22.6.1.3.3-11
Information Element	Value/Remark	Comment	Condition
Destination Address	172.168.9.1	Significant for packet filter 1, 2 and 3. Value does not match packet filters 1, 2 or 3.	IPv4
	2001:0bb0::0001:0001	Significant for packet filter 1, 2, 3 and 4. Value does not match packet filters 1, 2, 3 or 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1.3.3-8: IP packet#2 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#5, Table 22.6.1.3.3-11

Information Element

Value/Remark

Comment

Condition

Protocol

TCP

Significant packet filters 1, 2 and 3. Value does not match packet filters 1, 2 or 3.

Table 22.6.1.3.3-9: IP packet#3 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#5, Table 22.6.1.3.3-11
Information Element	Value/Remark	Comment	Condition
Source Port	60101	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.

Table 22.6.1.3.3-10: IP packet#4 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#5, Table 22.6.1.3.3-11
Information Element	Value/Remark	Comment	Condition
Destination Port	60451	Significant for packet filters 1 and 2. Value does not match packet filter 1 or 2.

Table 22.6.1.3.3-11: IP packet#5 (step 3, Table 22.6.1.3.2-2)

Derivation path: IETF RFC 791 section 3.1 (IPv4) or RFC 2460 section 3 (IPv6) and RFC 769 introduction
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10101001	Significant for packet filters 1, 2, 3, and 4. Value matches packet filters 1 and 2. Value does not match packet filters 3 or 4.
Protocol	17	UDP Significant packet filters 1, 2 and 3. Value matches packet filters 1 and 2. Value does not match packet filter 3.
Source Address	192.168.0.1	Not significant for any packet filters	IPv4
	fe80::1:1	Not significant for any packet filters	IPv6
Destination Address	172.168.8.1	Significant for packet filters 1, 2 and 3. Value matches packet filters 1, 2 and 3.	IPv4
	2001:0ba0::0001:0001	Significant for packet filters 1, 2, 3 and 4. Value matches packet filters 1, 2, 3 and 4.	IPv6
Source Port	60001	Significant for packet filters 1 and 2. Value matches packet filters 1 and 2.
Destination Port	60350	Significant for packet filters 1 and 2. Value matches packet filters 1 and 2.
Flow Label	10	Significant for packet filter 4. Value does not match packet filter 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1.3.3-12: IP packet#6 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#9 Table 22.6.1.3.3-15
Information Element	Value/Remark	Comment	Condition
Destination Address	172.168.9.1	Significant for packet filter 1, 2 and 3. Value does not match packet filters 1, 2 or 3.	IPv4
	2001:0bb0::0001:0001	Significant for packet filter 1, 2, 3 and 4. Value does not match packet filters 1, 2, 3 or 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1.3.3-13: IP packet#7 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#9 Table 22.6.1.3.3-15

Information Element

Value/Remark

Comment

Condition

Protocol

TCP

Significant packet filters 1, 2 and 3. Value does not match packet filters 1, 2 or 3.

Table 22.6.1.3.3-14: IP packet#8 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#9 Table 22.6.1.3.3-15
Information Element	Value/Remark	Comment	Condition
IP Sec SPI range	0x0F90F0000	Significant for packet filter 3. Value does not match packet filter 3.

Table 22.6.1.3.3-15: IP packet#9 (step 3, Table 22.6.1.3.2-2)

Derivation path: IETF RFC 791 section 3.1 (IPv4) or RFC 2460 section 3 (IPv6) and RFC 769 introduction
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10100010	Significant for packet filters 1, 2, 3, and 4. Value matches packet filter 3. Value does not match packet filters 1, 2 or 4.
Protocol	50	IPSec (ESP) Significant packet filters 1, 2 and 3. Value matches packet filter 3. Value does not match packet filters 1 or 2.
Source Address	192.168.0.1	Not significant for any packet filters	IPv4
	Fe80::1:1	Not significant for any packet filters	IPv6
Destination Address	172.168.8.1	Significant for packet filters 1, 2 and 3. Value matches packet filters 1, 2 and 3.	IPv4
	2001:0ba0::0001:0001	Significant for packet filters 1, 2, 3 and 4. Value matches packet filters 1, 2, 3 and 4.	IPv6
Source Port	60101	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
Destination Port	60451	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
IP Sec SPI range	0x0F80F0000	Significant for packet filter 3. Value matches packet filter 3.
Flow Label	10	Significant for packet filter 4. Value does not match packet filter 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1.3.3-16: IP packet#10 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#12, Table 22.6.1.3.3-18

Information Element

Value/Remark

Comment

Condition

Destination Address

2001:0bb0::0001:0001

IPv6

Significant for packet filter 1, 2, 3 and 4. Value does not match packet filters 1, 2, 3 or 4.

Table 22.6.1.3.3-17: IP packet#11 (step 3, Table 22.6.1.3.2-2)

Derivation path: IP packet#12, Table 22.6.1.3.3-18
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	11101001	Significant for packet filters 1, 2, 3 and 4. Value does not match packet filters 1, 2, 3 or 4.

Table 22.6.1.3.3-18: IP packet#12 (step 3, Table 22.6.1.3.2-2)

Derivation path: RFC 2460 section 3 (IPv6) and RFC 769 introduction
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10110011	Significant for packet filters 1, 2, 3, and 4. Value matches packet filter 4. Value does not match packet filters 1, 2 or 3.
Protocol	6	TCP Significant packet filters 1, 2 and 3. Value does not match packet filters 1, 2 or 3.
Source Address	Fe80::1:1	IPv6 Not significant for any packet filters
Destination Address	2001:0ba0::0001:0001	IPv6 Significant for packet filters 1, 2, 3 and 4. Value matches packet filters 1, 2, 3 and 4.
Source Port	60101	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
Destination Port	60451	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
Flow Label	5	IPv6 Significant for packet filter 4. Value matches packet filter 4.

Table 22.6.1.3.3-19 to -23: Void

Table 22.6.1.3.3-24: IP packet#13 (step 7, Table 22.6.1.3.2-2)

Derivation path: IETF RFC 791 section 3.1 (IPv4) or RFC 2460 section 3 (IPv6) and RFC 769 introduction
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10101010	Significant for packet filters 1, 2, 3, and 4. Value matches packet filter 1 and 2. Value does not match packet filters 3 or 4.
Protocol	6	TCP Significant packet filters 1, 2 and 3Value does not match packet filters 1, 2 or 3.
Source Address	192.168.0.1	Not significant for any packet filters	IPv4
	Fe80::1:1	Not significant for any packet filters	IPv6
Destination Address	172.168.8.1	Significant for packet filters 1, 2, 3 and 5. Value matches packet filters 1, 2, 3 and 5.	IPv4
	2001:0ba0: :0001:0001	Significant for packet filters 1, 2, 3, 4 and 5. Value matches packet filters 1, 2, 3, 4 and 5.	IPv6
Source Port	60101	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
Destination Port	60451	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
Flow Label	10	Significant for packet filter 4. Value does not match packet filter 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1.3.3-25: IP packet#14 (step 7, Table 22.6.1.3.2-2)

Derivation path: IP packet#13, Table 22.6.1.3.3-24
Information Element	Value/Remark	Comment	Condition
Destination Address	172.168.9.1	Significant for packet filters 1, 2, 3 and 5. Value does not match packet filters 1, 2, 3 and 5.	IPv4
	2001:0ba1::0001:0001	Significant for packet filters 1, 2, 3, 4 and 5. Value does not match packet filters 1, 2, 3, 4 and 5.	IPv6

Table 22.6.1.3.3-25A: Void

Table 22.6.1.3.3-26: Message PDN CONNECTIVITY REQUEST (step 16a5, Table 22.6.1.3.2-3)

Derivation Path: TS 36.508 Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	UE assigns a particular PTI not yet used between 1 and 254
ESM information transfer flag	Not present	This IE is only used during an attach procedure.
Access point name	APN-1(New PDN name)	The requested PDN is different from default PDN

Table 22.6.1.3.3-27: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 16a6, Table 22.6.1.3.2-3)

Derivation Path: TS 36.508 Table 4.7.3-6
Information Element	Value/remark	Comment	Condition
EPS bearer identity	6
Procedure transaction identity	PTI-1	SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure.
Access point name	APN-1	SS re-uses the particular APN defined by UE for this present additional PDN connectivity request procedure

Table 22.6.1.3.3-28: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 16a8, Table 22.6.1.3.2-3)

Derivation Path: TS 36.508 Table 4.7.3-4
Information Element	Value/remark	Comment	Condition
EPS bearer identity	6
Procedure transaction identity	0	No procedure transaction identity assigned

Table 22.6.1.3.3-29: Message PDN DISCONNECT REQUEST (step 16a13, Table 22.6.1.3.2-3)

Derivation Path: TS 36.508 Table 4.7.3-22
Information Element	Value/remark	Comment	Condition
EPS bearer identity	‘0000’	"no EPS bearer identity assigned"
Procedure transaction identity	PTI-1	UE assigns a particular PTI not yet used between 1 and 254
Linked EPS bearer identity	6

Table 22.6.1.3.3-30: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 16a14, Table 22.6.1.3.2-3)

Derivation Path: TS 36.508 Table 4.7.3-12
Information Element	Value/remark	Comment	Condition
EPS bearer identity	6	SS re-uses the EPS Bearer Id defined by UE for this present PDN disconnection procedure.
Procedure transaction identity	PTI-1	SS re-uses the particular PTI defined by UE for this present PDN disconnection procedure.	UE-INITIATED
ESM cause	#36	regular deactivation

Table 22.6.1.3.3-31: Message DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 16a15, Table 22.6.1.3.2-3)

Derivation Path: TS 36.508 Table 4.7.3-11
Information Element	Value/remark	Comment	Condition
EPS bearer identity	6	The same value as the value set in DEACTIVATE EPS BEARER CONTEXT REQUEST message.
Procedure transaction identity	0	No procedure transaction identity assigned

22.6.1a NB-IoT / UE routing of uplinks packets / Control Plane

22.6.1a.1.1 Test Purpose (TP)

(1)

with { the UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-CONNECTED mode with a default EPS bearer active }

ensure that {

when { the UE has IP packets for transmission where each IP packet matches at least one of the different packet filters configured in the UL TFTs for the default EPS }

then { the UE evaluates the packet filters in the correct evaluation order and transmits IP packets in uplink on the default EPS bearer }

}

(2)

with { the UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-CONNECTED mode with a default EPS bearer active }

ensure that {

when { the UE has an IP packet for transmission where the IP header does not satisfy any of the configured packet filters in the UL TFT configured for the default EPS bearer }

then { the UE discards the IP packet }

}

22.6.1a.1.2 Conformance requirements

The conformance requirements covered in the current TC are the same as in section 22.6.1.1.2.

22.6.1a.1.3 Test description

22.6.1a.1.3.1 Pre-test conditions

System Simulator:

– NB-IoT Ncell 1, default parameter;

UE:

– None

Preamble:

– The UE is in state Switched OFF (State 1)

22.6.1a.1.3.2 Test procedure sequence

Table 22.6.1a.3.2-1: Packet filters

Packet filter components

Packet filter ID

UL TFT

Packet filter evaluation precedence

Protocol Number (IPv4) / Next Header (IPv6)

Remote address and Subnet mask

Single Local Port

(UE)

Local Port Range

(UE)

Single Remote Port

(NW)

Remote Port Range

(NW)

IPSec SPI range

Type of Service (IPv4) / Traffic Class (IPv6) and Mask

Flow Label (IPv6)

Comments

DRB2

(UDP)

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

60001

–

60350:

60450

–

10101000, Mask=
11111100

–

UDP application identified by remote address, type of service/traffic class and specific local and remote port numbers

This is a valid Packet Filter Attribute Combination Type I according to TS 23.060, subclause 15.3.2.0.

DRB2

(UDP)

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

–

60000:60100

–

60350

–

10101000, Mask=
11111100

–

DRB2

50
IPSec (ESP)

IPv4:

172.168.8.0 [255.255.255.0]

IPv6:

2001:0ba0:: [ffff:ffff::]

–

0x0F80F0000

10100000, Mask=
11111100

–

IPSec session. Example from TS 23.060 clause 15.3.3.3

This is a valid Packet Filter Attribute Combination Type II according to TS 23.060, subclause 15.3.2.0.

DRB2

–

IPv6:

2001:0ba0:: [ffff:ffff::]

–

10110000, Mask=
11111100

IPv6 Flow Label filter.

This is a valid Packet Filter Attribute Combination Type III according to TS 23.060, subclause 15.3.2.0.

Table 22.6.1a.3.2-2: Sub-test test parameters and test requirements

Sub-test Index	Test data (IP packet) Note	IP packet expected to be returned	Packet Filter Attribute Combination under test	Packet Filter Component under test	Comment
1	IP packet#1	Yes	Type I	All Type I packet filter components match	The IP packet is only matching Packet Filter 1 and 2 in Table 22.6.1a.3.2-1. The IP packet is returned as Packet Filter 1 is evaluated before Packet Filter 2.
2	IP packet#2	Yes	Type I	Single local port does not match	The IP packet is only matching Packet Filter 2 in Table 22.6.1a.3.2-1. The IP packet is returned.
3	IP packet#3	Yes	Type I	Single remote port does not match	IP packet is only matching Packet Filter 1 in Table 22.6.1a.3.2-1. The IP packet is returned.
4	IP packet#4	Yes	Type II	All Type II packet filter components match	The IP packet is only matching Packet Filter 3 in Table 22.6.1a.3.2-1. The IP packet is returned.
5	IP packet#5	Yes	Type III	All Type III packet filter components match	The IP packet is only matching Packet Filter 4 in Table 22.6.1a.3.2-1. The IP packet is returned.
6	IP packet#6	No	Type I	Remote Address does not match	IP packet does not match any Packet Filters.
7	IP packet#7	No	Type II	Remote Address does not match	IP packet does not match any Packet Filters.
8	IP packet#8	No	Type II	Protocol identifier/Next header does not match	IP packet does not match any Packet Filters.
9	IP packet#9	No	Type II	Security parameter index does not match	IP packet does not match any Packet Filters.
10	IP packet#10	No	Type III	Remote Address does not match	IP packet does not match any Packet Filters.
11	IP packet#11	No	Type III	Flow Label does not match	IP packet does not match any Packet Filters.
Note: IP Packet details are specified in Tables 22.6.1a.3.3-5 to 22.6.1a.3.3-16 in clause 22.6.1a.3.3.

The test procedure in Table 22.6.1a.3.2-4, is executed once for IPv4 case (sub test 1) and once for IPv6 case (sub test 2) dependent on UE capability as specified in Table 22.6.1a.3.2-3.

Table 22.6.1a.3.2-3: Test executions and test parameters

Sub test	Applicability	IPtyp
1	UE supporting IPv4	‘IPv4’
2	UE supporting IPv6	‘IPv6’
Note 1: For UEs supporting both IPv4 and IPv6 then both test execution 1 and 2 shall be performed.

Table 22.6.1a.1.3.2-4: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS performs the generic procedure in subclause 8.1.5.2A in 36.508 to get UE in the Test Mode Activated (State 2A-NB) state with test loop mode I on Ncell1 establishing a default EPS bearer.	–	–	–	–
2	The SS performs the generic procedure in subclause 8.1.5.2B in [18] to get UE in the Test Loopback Activated (State 2B-NB) with test loop mode I.	–	–	–	–
3	The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message to add TFT to the default EPS bearer. This message is included in a DLInformationTransfer-NB message.	<–	MODIFY EPS BEARER CONTEXT REQUEST	–	–
4	UE transmits a MODIFY EPS BEARER CONTEXT ACCEPT message. This message is included in a DLInformationTransfer-NB message.	–>	MODIFY EPS BEARER CONTEXT ACCEPT	–	–
–	EXCEPTION: IF IPtype=’IPv4′ then test steps 5 to 6 are repeated for N = 1 to 4 using the IPv4 packet filters components in Table 22.6.1a.3.2-1. IF IPtype=’IPv6′ then test steps 5 to 6 are repeated for N = 1 to 5 using the IPv6 packet filters components in Table 22.6.1a.3.2-1.	–	–	–	–
5	The SS transmits one IP Packet according to Table 22.6.1a.3.2-2 for Sub-test index=N	–	–	–	–
6	Check: Does the UE return the IP Packet as specified by Table 22.6.1a.3.2-2 for Sub-test index=N?	–	–	1	P
–	EXCEPTION: IF IPtype=’IPv4′ then test steps 7 to 8 are repeated for N = 6 to 9 using the IPv4 packet filters components in Table 22.6.1a.3.2-1. IF IPtype=’IPv6′ then test steps 7 to 8 are repeated for N = 6 to 11 using the IPv6 packet filters components in Table 22.6.1a.3.2-1.	–	–	–	–
7	The SS transmits one IP Packet according to Table 22.6.1a.3.2-2 for Sub-test index=N	–	–	–	–
8	Check: Does the UE send an IP Packet?	–	–	2	F
9	The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode.	<–	RRC: DLInformationTransfer-NB TC: OPEN UE TEST LOOP	–	–
10	The UE transmits an OPEN UE TEST LOOP COMPLETE message.	–>	RRC: ULInformationTransfer-NB TC: OPEN UE TEST LOOP COMPLETE	–	–
11	The SS transmits an DEACTIVATE TEST MODE message to de-activate UE radio bearer test mode procedure.	<–	RRC: DLInformationTransfer-NB TC: DEACTIVATE TEST MODE	–	–
12	The UE transmits an DEACTIVATE TEST MODE COMPLETE message.	–>	RRC: ULInformationTransfer-NB TC: DEACTIVATE TEST MODE COMPLETE	–	–
–	EXCEPTION: If this is the first of two executions according to table 22.6.1a.3.2-3, step 13 is performed, otherwise the test is continued from step 14.
13	The UE is switched OFF, see Note 1. The test is restarted from step 1.	–	–	–	–
14	The SS releases the RRC connection	–>	RRC: RRCConnectionRelease-NB	–	–
Note 1: This implies detaching of the UE, releasing of the RRC connection and resetting of the radio bearers at the SS side.

22.6.1a.1.3.3 Specific message contents

Table 22.6.1a.3.3-1: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Test execution 1: step 1, Table 22.6.1a.3.2-4)

Derivation Path: 36.508 table 4.7.3-6
Information Element		Value/remark		Comment	Condition
PDN address
Length of PDN address contents	5 octets
PDN type value	‘001’B		IPv4
PDN address information	IPv4 address		The SS provides a valid IPv4 address
ESM cause		IF "PDN type" IE in step 4 (preamble) is ‘IPv4v6’ THEN ‘00110010’B ELSE Not present		"PDN type IPv4 only allowed"

Table 22.6.1a.3.3-2: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Test execution 2: step 1, Table 22.6.1a.3.2-4)

Derivation Path: 36.508 table 4.7.3-6
Information Element		Value/remark		Comment	Condition
PDN address
Length of PDN address contents	9 octets
PDN type value	‘010’B		IPv6
PDN address information	IPv6 interface identifier		The SS provides a valid IPv6 interface identifier
ESM cause		IF "PDN type" IE in step 4 (preamble) is ‘IPv4v6’ THEN ‘00110011’B ELSE Not present		"PDN type IPv6 only allowed"

Table 22.6.1a.3.3-3: Message MODIFY EPS BEARER CONTEXT REQUEST (step 3, Table 22.6.1a.3.2-4)

Derivation path: 36.508 table 4.7.3-16 and table 4.6.1-3
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message	SS assigns the current default EPS bearer context.
Procedure transaction identity	0	"No procedure transaction identity assigned"
TFT
TFT operation code	“Create new TFT”
E bit	0
Packet filters (Note 1)	1, 2, 3		IPv4
Packet filters (Note 1)	1, 2, 3, 4		IPv6
Note 1: This row refers to the packet filters defined in Table 22.6.1a.3.2-1.

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1a.3.3-4: Message MODIFY EPS BEARER CONTEXT ACCEPT (step 4, Table 22.6.1a.3.2-4)

Derivation path: 36.508 table 4.7.3-14
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	The same value as the value set in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message	Same value as in MODIFY EPS BEARER CONTEXT REQUEST
Procedure transaction identity	0	"No procedure transaction identity assigned"

Table 22.6.1a.3.3-5: IP packet#1 (step 5, Table 22.6.1a.3.2-2)

Derivation path: IETF RFC 791 section 3.1 (IPv4) or RFC 2460 section 3 (IPv6) and RFC 769 introduction
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10101001	Significant for packet filters 1, 2, 3, and 4. Value matches packet filters 1 and 2. Value does not match packet filters 3 or 4.
Protocol	17	UDP Significant packet filters 1, 2 and 3. Value matches packet filters 1 and 2. Value does not match packet filter 3.
Source Address	192.168.0.1	Not significant for any packet filters	IPv4
	fe80::1:1	Not significant for any packet filters	IPv6
Destination Address	172.168.8.1	Significant for packet filters 1, 2 and 3. Value matches packet filters 1, 2 and 3.	IPv4
	2001:0ba0::0001:0001	Significant for packet filters 1, 2, 3 and 4. Value matches packet filters 1, 2, 3 and 4.	IPv6
Source Port	60001	Significant for packet filters 1 and 2. Value matches packet filters 1 and 2.
Destination Port	60350	Significant for packet filters 1 and 2. Value matches packet filters 1 and 2.
Flow Label	10	Significant for packet filter 4. Value does not match packet filter 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1a.3.3-6: IP packet#2 (step 5, Table 22.6.1a.3.2-2)

Derivation path: IP packet#1, Table 22.6.1a.3.3-5
Information Element	Value/Remark	Comment	Condition
Source Port	60002	Significant for packet filters 1 and 2. Value matches packet filter 2. Value does not match packet filter 1.

Table 22.6.1a.3.3-7: IP packet#3 (step 5, Table 22.6.1a.3.2-2)

Derivation path: IP packet#1, Table 22.6.1a.3.3-5
Information Element	Value/Remark	Comment	Condition
Destination Port	60351	Significant for packet filters 1 and 2. Value matches packet filter 1. Value does not match packet filter 2

Table 22.6.1a.3.3-8: IP packet#4 (step 5, Table 22.6.1a.3.2-2)

Derivation path: IETF RFC 791 section 3.1 (IPv4) or RFC 2460 section 3 (IPv6) and RFC 769 introduction
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10100010	Significant for packet filters 1, 2, 3, and 4. Value matches packet filter 3. Value does not match packet filters 1, 2 or 4.
Protocol	50	IPSec (ESP) Significant packet filters 1, 2 and 3. Value matches packet filter 3. Value does not match packet filters 1 or 2.
Source Address	192.168.0.1	Not significant for any packet filters	IPv4
	Fe80::1:1	Not significant for any packet filters	IPv6
Destination Address	172.168.8.1	Significant for packet filters 1, 2 and 3. Value matches packet filters 1, 2 and 3.	IPv4
	2001:0ba0::0001:0001	Significant for packet filters 1, 2, 3 and 4. Value matches packet filters 1, 2, 3 and 4.	IPv6
Source Port	60101	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
Destination Port	60451	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
IP Sec SPI range	0x0F80F0000	Significant for packet filter 3. Value matches packet filter 3.
Flow Label	10	Significant for packet filter 4. Value does not match packet filter 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1a.3.3-9: IP packet#5 (step 5, Table 22.6.1a.3.2-2)

Derivation path: RFC 2460 section 3 (IPv6) and RFC 769 introduction
Information Element	Value/Remark	Comment	Condition
Type of service (IPv4) / Traffic Class (IPv6)	10110011	Significant for packet filters 1, 2, 3, and 4. Value matches packet filter 4. Value does not match packet filters 1, 2 or 3.
Protocol	6	TCP Significant packet filters 1, 2 and 3. Value does not match packet filters 1, 2 or 3.
Source Address	Fe80::1:1	IPv6 Not significant for any packet filters
Destination Address	2001:0ba0::0001:0001	IPv6 Significant for packet filters 1, 2, 3 and 4. Value matches packet filters 1, 2, 3 and 4.
Source Port	60101	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
Destination Port	60451	Significant for packet filters 1 and 2. Value does not match packet filters 1 or 2.
Flow Label	5	IPv6 Significant for packet filter 4. Value matches packet filter 4.

Table 22.6.1a.3.3-10: IP packet#6 (step 7, Table 22.6.1a.3.2-2)

Derivation path: IP packet#1, Table 22.6.1a.3.3-5
Information Element	Value/Remark	Comment	Condition
Destination Address	172.168.9.1	Significant for packet filter 1, 2 and 3. Value does not match packet filters 1, 2 or 3.	IPv4
	2001:0bb0::0001:0001	Significant for packet filter 1, 2, 3 and 4. Value does not match packet filters 1, 2, 3 or 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1a.3.3-11: IP packet#7 (step 7, Table 22.6.1a.3.2-2)

Derivation path: IP packet#4 Table 22.6.1a.3.3-8
Information Element	Value/Remark	Comment	Condition
Destination Address	172.168.9.1	Significant for packet filter 1, 2 and 3. Value does not match packet filters 1, 2 or 3.	IPv4
	2001:0bb0::0001:0001	Significant for packet filter 1, 2, 3 and 4. Value does not match packet filters 1, 2, 3 or 4.	IPv6

Condition	Explanation
IPv4	This condition applies if test variable IP type is set to ‘IPv4’.
IPv6	This condition applies if test variable IP type is set to ‘IPv6’.

Table 22.6.1a.3.3-12: IP packet#8 (step 7, Table 22.6.1a.3.2-2)

Derivation path: IP packet#4 Table 22.6.1a.3.3-8

Information Element

Value/Remark

Comment

Condition

Protocol

TCP

Significant packet filters 1, 2 and 3. Value does not match packet filters 1, 2 or 3.

Table 22.6.1a.3.3-13: IP packet#9 (step 7, Table 22.6.1a.3.2-2)

Derivation path: IP packet#4 Table 22.6.1a.3.3-8
Information Element	Value/Remark	Comment	Condition
IP Sec SPI range	0x0F90F0000	Significant for packet filter 3. Value does not match packet filter 3.

Table 22.6.1a.3.3-14: IP packet#10 (step 7, Table 22.6.1a.3.2-2)

Derivation path: IP packet#5, Table 22.6.1a.3.3-9

Information Element

Value/Remark

Comment

Condition

Destination Address

2001:0bb0::0001:0001

IPv6

Significant for packet filter 1, 2, 3 and 4. Value does not match packet filters 1, 2, 3 or 4.

Table 22.6.1a.3.3-15: IP packet#11 (step 7, Table 22.6.1a.3.2-2)

Derivation path: IP packet#5, Table 22.6.1a.3.3-9

Information Element

Value/Remark

Comment

Condition

Flow Label

IPv6

Significant for packet filter 4. Value does not match packet filter 4.

22.6.2 NB-IoT / UE requested bearer resource modification accepted by the network / Default EPS bearer context

22.6.2.1 Test Purpose (TP)

(1)

with { UE in PROCEDURE TRANSACTION INACTIVE state and in EMM-CONNECTED mode }

ensure that {

when { UE is requested to modify of bearer resource corresponding to the default bearer }

then { UE sends a BEARER RESOURCE MODIFICATION REQUEST message }

}

(2)

with { UE having sent the BEARER RESOURCE MODIFICATION REQUEST message }

ensure that {
when { UE receives a MODIFY EPS BEARER CONTEXT REQUEST message with the procedure transaction identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message }

then { UE sends a MODIFY EPS BEARER CONTEXT ACCEPT message }

}

22.6.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.4.3.3, 6.5.3.3, 6.5.4.2 and 6.5.4.3.

[TS 24.301, clause 6.4.3.3]

If the MODIFY EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]), the UE uses the PTI to identify the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to which the EPS bearer context modification is related (see subclause 6.5.3 and subclause 6.5.4).

If the MODIFY EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007 [12]) and the PTI is associated to a UE requested bearer resource allocation procedure or a UE requested bearer resource modification procedure, the UE shall release the traffic flow aggregate description associated to the PTI value provided.

[TS 24.301, clause 6.5.3.3]

If the MODIFY EPS BEARER CONTEXT REQUEST message is received, the UE verifies that the EPS bearer identity given in the EPS bearer identity IE is any of the active EPS bearer contexts. The UE shall then proceed as described in subclause 6.4.3.3 or subclause 6.4.3.4.

[TS 24.301, clause 6.5.4.2]

In order to request the modification of bearer resources for one traffic flow aggregate, the UE shall send a BEARER RESOURCE MODIFICATION REQUEST message to the MME, start timer T3481 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.4.2.1).

[TS 24.301, clause 6.5.4.3]

Upon receipt of the BEARER RESOURCE MODIFICATION REQUEST message, the MME checks whether the resources requested by the UE can be established, modified or released by verifying the EPS bearer identity given in the EPS bearer identity for packet filter IE.

If the bearer resource modification requested is accepted by the network, the MME shall initiate either a dedicated EPS bearer context activation procedure, an EPS bearer context modification procedure or an EPS bearer context deactivation procedure.

22.6.2.3 Test description

22.6.2.3.1 Pre-test conditions

System Simulator:

– Ncell 50

UE:

None.

Preamble:

– The UE is in Attach Connected Mode (state 2-NB) with no dedicated EPS bearers activated according to [18].

– A default EPS bearer is established between the first PDN and the UE.

22.6.2.3.2 Test procedure sequence

Table 22.6.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Cause the UE to request bearer resource modification of default EPS bearer associated with first PDN connectivity.(see Note 1)	–	–	–	–
2	Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?	–>	BEARER RESOURCE MODIFICATION REQUEST	1	P
3	The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message. This message is included in a DLInformationTransfer message.	<–	MODIFY EPS BEARER CONTEXT REQUEST	–	–
4	Check: Does the UE transmit a MODIFY EPS BEARER CONTEXT ACCEPT message?	–>	MODIFY EPS BEARER CONTEXT ACCEPT	2	P
Note 1: The request is assumed to be triggered by AT command +CGCMOD.

22.6.2.3.3 Specific message contents

Table 22.6.2.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, Table 22.6.2.3.2-1)

Derivation path: 36.508 table 4.7.3-8
Information Element	Value/Remark	Comment	Condition
EPS bearer identity for packet filter	5
Traffic flow aggregate
TFT operation code	Any allowed value

Table 22.6.2.3.3-2: Message MODIFY EPS BEARER CONTEXT REQUEST (step 3, Table 22.6.2.3.2-1)

Derivation path: 36.508 table 4.7.3-18, condition UE-INITIATED
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	5
TFT
TFT operation code	“Create new TFT”
E bit	0
Packet filters (Note 1)	1
Note 1: This row refers to the packet filters defined in Table 22.6.2.3.3-3.

Table 22.6.2.3.3-3: Message MODIFY EPS BEARER CONTEXT REQUEST (step 3, Table 22.6.2.3.2-1)

Packet filter components

Packet filter ID

UL TFT

Packet filter evaluation precedence

Protocol Number (IPv4) / Next Header (IPv6)

Remote address and Subnet mask

Single Local Port

(UE)

Remote Port Range

(NW)

Type of Service (IPv4) / Traffic Class (IPv6) and Mask

DRB1

(UDP)

IPv4:

172.168.8.0 [255.255.255.255]

IPv6:

2001:0ba0:: [ffff:ffff::]

60001

60350:

60450

10101000, Mask=
11111100

22.6.3 NB-IoT / UE requested bearer resource modification error handling (Resource modification not accepted by the network) / Expiry of timer T3481/ Default EPS bearer context

22.6.3.1 Test Purpose (TP)

(1)

with { UE has sent the BEARER RESOURCE MODIFICATION REQUEST message }

ensure that {
when { UE receives a BEARER RESOURCE MODIFICATION REJECT message with the procedure transaction identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message and a cause “Protocol error, unspecified” }

then { UE enters state PROCEDURE TRANSACTION INACTIVE }

}

(2)

with { UE in connected mode }

ensure that {
when { UE receives a MODIFY EPS BEARER CONTEXT REQUEST message with a non existent procedure transaction identity (PTI) with the EPS bearer identity pointing at the default EPS bearer context }

then { UE sends a MODIFY EPS BEARER CONTEXT REJECT message }

}

(3)

with { UE has sent a BEARER RESOURCE MODIFICATION REQUEST message }

ensure that {
when { UE detects less than fifth expiry of timer T3481 }

then { UE re-sends a BEARER RESOURCE MODIFICATION REQUEST message }

}

(4)

with { UE has sent a BEARER RESOURCE MODIFICATION REQUEST message }

ensure that {
when { UE detects the fifth expiry of timer T3481 }

then { UE release the PTI allocated for this action and enter the state PROCEDURE TRANSACTION INACTIVE }

}

22.6.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.5.4.3, 6.5.4.4, 6.5.4.5 and 7.3.1.

[TS 24.301, clause 6.5.4.3]

[TS 24.301, clause 6.5.4.4]

If the bearer resource modification requested cannot be accepted by the network, the MME shall send a BEARER RESOURCE MODIFICATION REJECT message to the UE. The message shall contain the PTI and an ESM cause value indicating the reason for rejecting the UE requested bearer resource modification.

The ESM cause value typically indicates one of the following:

#26: insufficient resources;

#30: request rejected by Serving GW or PDN GW;

#31: request rejected, unspecified;

#32: service option not supported;

#33: requested service option not subscribed;

#34: service option temporarily out of order;

#35: PTI already in use;

#37: EPS QoS not accepted;

#41: semantic error in the TFT operation;

#42: syntactical error in the TFT operation;

#43: invalid EPS bearer identity;

#44: semantic error(s) in packet filter(s);

#45: syntactical error(s) in packet filter(s);

#56: collision with network initiated request;

#59: unsupported QCI value;

#60: bearer handling not supported; or

#95 – 111: protocol errors.

…

Upon receipt of a BEARER RESOURCE MODIFICATION REJECT message, the UE shall stop the timer T3481, release the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE TRANSACTION INACTIVE. If the ESM cause included in the BEARER RESOURCE MODIFICATION REJECT message is #43 "invalid EPS bearer identity", the UE locally deactivates the EPS bearer context(s) without peer-to-peer ESM signalling.

[TS 24.301, clause 6.5.4.5]

The following abnormal cases can be identified:

a) Expiry of timer T3481:

On the first expiry of the timer T3481, the UE shall resend the BEARER RESOURCE MODIFICATION REQUEST and shall reset and restart timer T3481. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3481, the UE shall abort the procedure, release the PTI allocated for this activation and enter the state PROCEDURE TRANSACTION INACTIVE. In addition, if the UE had initiated resource release for all the traffic flows for the bearer, it shall deactivate the EPS bearer context locally without peer-to-peer signalling between the UE and the MME. In order to synchronize the EPS bearer context status with the MME, on indication of "back to E-UTRAN coverage" from the lower layers, the UE shall send a TRACKING AREA UPDATE REQUEST message that includes the EPS bearer context status IE to the MME.

b) Unknown EPS bearer context

Upon receipt of the BEARER RESOURCE MODIFICATION REJECT message including ESM cause #43 "invalid EPS bearer identity", the UE shall deactivate the existing EPS bearer context locally without peer-to-peer signalling between the UE and the MME.

c) Collision of a UE requested bearer resource modification procedure and an EPS bearer context deactivation procedure.

When the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message during the bearer resource modification procedure, and the EPS bearer identity indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST message is a EPS bearer context the UE indicated in the UE requested bearer resource modification procedure, then the UE shall abort the UE requested bearer resource modification procedure and proceed with the EPS bearer context deactivation procedure.

[TS 24.301, clause 7.3.1]

The following network procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in an ESM message:

…

j) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message in which the PTI value is an assigned value that does not match any PTI in use, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including ESM cause #47 "PTI mismatch".

22.6.3.3 Test description

22.6.3.3.1 Pre-test conditions

System Simulator:

– Ncell 50

UE:

None.

Preamble:

– The UE is in Attach Connected Mode (state 2-NB) 1 default EPS and no dedicated EPS bearers activated according to [18].

22.6.3.3.2 Test procedure sequence

Table 22.6.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Cause the UE to request bearer resource modification of default EPS bearer associated with first PDN connectivity.(see Note 2)	–	–	–	–
2	The UE transmits a BEARER RESOURCE MODIFICATION REQUEST message.	–>	BEARER RESOURCE MODIFICATION REQUEST	–	–
3	The SS transmits a BEARER RESOURCE MODIFICATION REJECT message.	<–	BEARER RESOURCE MODIFICATION REJECT	–	–
4	SS waits for 500ms (Note 1).	–	–	–	–
5	The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message. This message is included in a DLInformationTransfer message.	<–	MODIFY EPS BEARER CONTEXT REQUEST	–	–
6	Check: Does the UE transmit a MODIFY EPS BEARER CONTEXT REJECT message?	–>	MODIFY EPS BEARER CONTEXT REJECT	1, 2	P
6A	Cause the UE to request bearer resource modification of default EPS bearer associated with first PDN connectivity.(see Note 2)	–	–	–	–
7	The UE transmits a BEARER RESOURCE MODIFICATION REQUEST message.	–>	BEARER RESOURCE MODIFICATION REQUEST	–	–
8	Wait for 188 s to ensure that T3481 expires (1^st expiry).	–	–	–	–
9	Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?	–>	BEARER RESOURCE MODIFICATION REQUEST	3	P
10	Wait for 188 s to ensure that T3481 expires (2^nd expiry).	–	–	–	–
11	Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?	–>	BEARER RESOURCE MODIFICATION REQUEST	3	P
12	Wait for 188 s to ensure that T3481 expires (3^rd expiry).	–	–	–	–
13	Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?	–>	BEARER RESOURCE MODIFICATION REQUEST	3	P
14	Wait for 188 s to ensure that T3481 expires (4^th expiry).	–	–	–	–
15	Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?	–>	BEARER RESOURCE MODIFICATION REQUEST	3	P
15A	Wait for 188 s to ensure that T3481 expires (5^th expiry).	–	–	–	–
16	The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message. This message is included in a DLInformationTransfer message.	<–	MODIFY EPS BEARER CONTEXT REQUEST	–	–
17	Check: Does the UE transmit a MODIFY EPS BEARER CONTEXT REJECT message?	–>	MODIFY EPS BEARER CONTEXT REJECT	2, 4	P
Note 1: The timer of 500ms is added to ensure that UE receives BEARER RESOURCE MODIFICATION REJECT message before the MODIFY EPS BEARER CONTEXT REQUEST message. Note 2: The request is assumed to be triggered by AT command +CGCMOD.

22.6.3.3.3 Specific message contents

Table 22.6.3.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (steps 2, 7, 9, 11, 13 and 15, Table 22.6.3.3.2-1)

Derivation path: 36.508 table 4.7.3-8
Information Element	Value/Remark	Comment	Condition
EPS bearer identity for packet filter	5

Table 22.6.3.3.3-2: Message BEARER RESOURCE MODIFICATION REJECT (step 3, Table 22.6.3.3.2-1)

Derivation path: 36.508 table 4.7.3-6A
Information Element	Value/Remark	Comment	Condition
ESM cause	‘0110 1111’B	Protocol error, unspecified

Table 22.6.3.3.3-3: Message MODIFY EPS BEARER CONTEXT REQUEST (steps 5 and 16, Table 22.6.3.3.2-1)

Derivation path: 36.508 table 4.7.3-18, condition NETWORK-INITIATED
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	5	default bearer
Procedure transaction identity	The same value as the value set in BEARER RESOURCE MODIFICATION REQUEST message in step 2.		Step 5
Procedure transaction identity	The same value as the value set in BEARER RESOURCE MODIFICATION REQUEST message in step 15.		Step 16

Table 22.6.3.3.3-4: Message MODIFY EPS BEARER CONTEXT REJECT (steps 6 and 17, Table 22.6.3.3.2-1)

Derivation path: 36.508 table 4.7.3-17
Information Element	Value/Remark	Comment	Condition
ESM cause	‘0010 1111’B	PTE mismatch
Procedure transaction identity	Any value

22.6.4 22.6.5 NB-IoT / UE requested PDN connectivity procedure not accepted / UE requested PDN connectivity accepted Dual priority T3396 override UE requested PDN connectivity accepted / Dual priority / T3346 override

22.6.5.1 Test Purpose (TP)

(1)

with { UE has sent a PDN CONNECTIVITY REQUEST message to an additional PDN }

ensure that {

when { UE receives an PDN CONNECTIVITY REJECT message with PTI matching the PDN CONNECTIVITY REQUEST message and including a ESM cause value }

then { UE enters the state PROCEDURE TRANSACTION INACTIVE }

}

(2)

with { the UE configured for low priority NAS signalling and low priority NAS signalling override and the UE has sent a PDN CONNECTIVITY REQUEST message indicating low NAS signalling priority }

ensure that {

when { the UE receives PDN CONNECTIVITY REJECT message with timer T3396 and ESM cause value #26 “insufficient resources” }

then { if higher layers in the UE request the activation of such a connection/context, the UE sends a PDN CONNECTIVITY REQUEST message with the low priority indicator set to “MS is not configured for NAS signalling low priority” }

}

(3)

with { the UE configured for dual priority NAS signalling and the UE has sent an EXTENDED SERVICE REQUEST message indicating low NAS signalling priority }

ensure that {

when { the UE receives SERVICE REJECT message with timer T3346 and EMM cause value #22 "Congestion" }

then { if higher layers in the UE request the activation of such a connection/context, the UE sends a PDN CONNECTIVITY REQUEST message with the low priority indicator set to "MS is not configured for NAS signalling low priority” }

}

22.6.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 4.2A, 5.6.1.6, 6.2.2, 6.4.1.3, 6.4.2.3, 6.5.1.2 and 6.5.5.

[TS 24.301, clause 4.2A]

A UE configured for NAS signalling low priority (see 3GPP TS 24.368 [15A], 3GPP TS 31.102 [17]) indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured for NAS signalling low priority", except for the following cases in which the UE shall set the low priority indicator to "MS is not configured for NAS signalling low priority":

– the UE is performing an attach for emergency bearer services;

– the UE has a PDN connection for emergency bearer services established and is performing EPS mobility management procedures, or is establishing a PDN connection for emergency bearer services;

– the UE configured for dual priority is requested by the upper layers to establish a PDN connection with the low priority indicator set to "MS is not configured for NAS signalling low priority";

– the UE configured for dual priority is performing EPS session management procedures related to the PDN connection established with low priority indicator set to "MS is not configured for NAS signalling low priority";

– the UE configured for dual priority has a PDN connection established by setting the low priority indicator to "MS is not configured for NAS signalling low priority" and is performing EPS mobility management procedures;

– the UE is performing a service request procedure for a CS fallback emergency call or 1xCS fallback emergency call;

– the UE is a UE configured to use AC11 – 15 in selected PLMN; or

– the UE is responding to paging.

The network may use the NAS signalling low priority indication for NAS level mobility management congestion control and APN based congestion control.

If the NAS signalling low priority indication is provided in a PDN CONNECTIVITY REQUEST message, the MME stores the NAS signalling low priority indication within the default EPS bearer context activated due to the PDN connectivity request procedure.

[TS 24.301, clause 5.6.1.6]

The following abnormal cases can be identified:

…

m) Timer T3346 is running

The UE shall not start the service request procedure unless:

– the UE receives a paging;

– the UE is a UE configured to use AC11 – 15 in selected PLMN;

– the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; or

– the UE is requested by the upper layer for a CS fallback for emergency call or a 1xCS fallback for emergency call; or

– the UE has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication and if the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, TRACKING AREA UPDATE REQUEST, EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority".

If the UE is in EMM-IDLE mode, the UE stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped.

Upon upper layer’s request for a mobile originated CS fallback which is not for emergency call, the UE in CS/PS mode 1 of operation shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer.

NOTE 6: If the UE disables the E-UTRA capability, then subsequent mobile terminating calls could fail.

Upon upper layer’s request for a CS fallback for emergency call, the UE may select GERAN or UTRAN radio access technology. It then proceeds with appropriate MM and CC specific procedures. The EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer.

Upon a request from the SMS entity to send an SMS and timer T3246 is not running, the UE, if operating in CS/PS mode 1 of operation, may select GERAN or UTRAN radio access technology. It then proceeds with the appropriate MM procedure.

NOTE 7: If the UE disables the E-UTRA capability, then subsequent mobile terminating calls could fail.

Upon upper layer’s request for a mobile originated 1x CS fallback which is not for emergency call, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS call procedures.

Upon upper layer’s request for a 1xCS fallback for emergency call, the UE may select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS call procedures.

[TS 24.301, clause 6.2.2]

The UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message, based on its IP stack configuration as follows:

a) A UE, which is Ipv6 and Ipv4 capable and

– has not been allocated an IP address for this APN, shall set the PDN type IE to Ipv4v6.

– has been allocated an Ipv4 address for this APN and received the ESM cause #52 “single address bearers only allowed”, and is requesting an Ipv6 address, shall set the PDN type IE to Ipv6.

– has been allocated an Ipv6 address for this APN and received the ESM cause #52 “single address bearers only allowed”, and is requesting an Ipv4 address, shall set the PDN type IE to Ipv4.

b) A UE, which is only Ipv4 capable, shall set the PDN type IE to Ipv4.

c) A UE, which is only Ipv6 capable, shall set the PDN type IE to Ipv6.

d) When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall set the PDN type IE to Ipv4v6.

…

[TS 24.301, clause 6.5.1.2]

…

In order to request connectivity to an additional PDN using a specific APN, the UE shall include the requested APN in the PDN CONNECTIVITY REQUEST message.

In the PDN type IE the UE shall either indicate the IP version capability of the IP stack associated with the UE or non IP as specified in subclause 6.2.2.

If the PDN type value of the PDN type IE is set to Ipv4 or Ipv6 or Ipv4v6 and the UE indicates “Control plane CioT EPS optimization supported” in the UE network capability IE of the ATTACH REQUEST message, the UE may include the Header compression configuration IE in the PDN CONNECTIVITY REQUEST message.

The UE shall set the request type to “initial request” when the UE is establishing a new PDN connectivity to a PDN in an attach procedure or in a stand-alone PDN connectivity procedure. The UE shall set the request type to “emergency” when the UE is requesting a new PDN connectivity for emergency bearer services. The UE shall set the request type to “handover” when the connectivity to a PDN is established upon handover from a non-3GPP access network and the UE was connected to that PDN before the handover to the 3GPP access network, or when the UE initiates the procedure to add 3GPP access to the PDN connection which is already established over WLAN.

…

[TS 24.301, clause 6.5.1.4]

…

If connectivity with the requested PDN cannot be accepted by the network, the MME shall send a PDN CONNECTIVITY REJECT message to the UE. The message shall contain the PTI and an ESM cause value indicating the reason for rejecting the UE requested PDN connectivity.

The ESM cause IE typically indicates one of the following ESM cause values:

#8: operator determined barring;

#26: insufficient resources;

#27: missing or unknown APN;

#28: unknown PDN type;

#29: user authentication failed;

#30: request rejected by Serving GW or PDN GW;

#31: request rejected, unspecified;

#32: service option not supported;

#33: requested service option not subscribed;

#34: service option temporarily out of order;

#35: PTI already in use;

#38: network failure;

#50: PDN type Ipv4 only allowed;

#51: PDN type Ipv6 only allowed;

#53: ESM information not received;

#54: PDN connection does not exist;

#55: multiple PDN connections for a given APN not allowed;

#95 – 111: protocol errors;

#112: APN restriction value incompatible with active EPS bearer context.

#113: Multiple accesses to a PDN connection not allowed.

[TS 24.301, clause 6.5.5]

If timer T3396 is running for a specific APN, because a PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396 and ESM cause value #26 "insufficient resources", or because the UE received a DEACTIVATE EPS BEARER CONTEXT REQUEST message containing a timer value for timer T3396 and ESM cause value #26 "insufficient resources" for a PDN connection established with low priority indicator set to "MS is configured for NAS signalling low priority", upon request of the upper layers the UE can:

– send a PDN CONNECTIVITY REQUEST message to the same APN, with low priority indicator set to "MS is not configured for NAS signalling low priority"; or,

– send a BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message, with low priority indicator set to "MS is not configured for NAS signalling low priority", for a PDN connection established with low priority indicator set to "MS is not configured for NAS signalling low priority" exists.

If timer T3396 is running, because any of the following messages containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396 and ESM cause value #26 "insufficient resources":

– a PDN CONNECTIVITY REQUEST without APN and with request type different from "emergency", sent together with an ATTACH REQUEST message;

– a stand-alone PDN CONNECTIVITY REQUEST message without APN and with request type different from "emergency"; or

– a BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message sent for a non-emergency PDN connection established without APN provided by the UE,

or because the UE received a DEACTIVATE EPS BEARER CONTEXT REQUEST message containing a timer value for timer T3396 and ESM cause value #26 "insufficient resources" for a non-emergency PDN connection established without APN provided by the UE and established with low priority indicator set to "MS is configured for NAS signalling low priority", then upon request of the upper layers the UE can initiate a new attach procedure or stand-alone PDN CONNECTIVITY REQUEST procedure without APN and with request type different from "emergency", with low priority indicator set to "MS is not configured for NAS signalling low priority".

For requests with low priority indicator set to "MS is configured for NAS signalling low priority", the UE shall follow the procedures specified in subclause 6.5.1.4.

22.6.5.3 Test description

22.6.5.3.1 Pre-test conditions

System Simulator:

– NB-IoT Ncell 1, default parameters.

UE:

– the UE is configured for NAS behaviour low priority

– the UE is configured for NAS behaviour low priority override

The UE is equipped with a USIM containing values shown in Table 22.6.5.3.1-1.

Table 22.6.5.3.1-1: USIM Configuration

USIM field	Value
EF_UST	Service 96 is supported.
EF_NASCONFIG	“NAS_SignallingPriority is set to NAS behaviour low priority” 4as defined in TS 24.368, clause 5.3.
EF_NASCONFIG	“Override_NAS_SignallingLowPriority is set to UE can override the NAS behaviour low priority indicator” as defined in TS 24.368, clause 5.9.
EF_NASCONFIG	“ExtendedAccessBarring is set to extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8
EF_NASCONFIG	“Override_ExtendedAccessBarring is set to UE can override extended access barring” as defined in TS 24.368, clause 5.10.
Note: As per TS 23.401 [22] clause 4.3.17.4, UE’s configuration of low access priority and Extended Access Barring shall match each other and so do their corresponding override configuration.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18] (1 default EPS bearer context is active).

22.6.5.3.2 Test procedure sequence

Table 22.6.5.3.2-1: Main Behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Cause the UE to request connectivity to an additional PDN (see Note)	–	–	–	–
2a1	IF pc_S1_U_DataTransfer AND pc_NB_MultiDRB THEN The UE transmits an CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST	–	–
2a2	The SS establishes DRB associated with the default EPS bearer context activated during the preamble (a first PDN obtained during the attach procedure).	–	–	–	–
2a3	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
2a4	The UE transmits a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN.	–>	PDN CONNECTIVITY REQUEST	–	–
2b1	ELSE The UE transmits a CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST	–	–
2b2	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
2b3	The UE transmits a PDN CONNECTIVITY REQUEST message	–>	PDN CONNECTIVITY REQUEST	–	–
3	The SS transmits a PDN CONNECTIVITY REJECT message.	<–	PDN CONNECTIVITY REJECT	–	–
4	The SS releases the RRC connection.	–	–	–	–
5	Cause the UE to request connectivity to an additional PDN (see Note)	–	–	–	–
6a1	IF pc_S1_U_DataTransfer AND pc_NB_MultiDRB THEN The UE transmits an CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST	–	–
6a2	The SS establishes DRB associated with the default EPS bearer context activated during the preamble (a first PDN obtained during the attach procedure).	–	–	–	–
6a3	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
6a4	Check: Does the UE transmit a PDN CONNECTIVITY REQUEST as specified to request an additional PDN?	–>	PDN CONNECTIVITY REQUEST	1	P
6b1	ELSE The UE transmits a CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST	–	–
6b2	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
6b3	Check: Does the UE transmit a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN?	–>	PDN CONNECTIVITY REQUEST	1	P
7	The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context.	<–	ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST	–	–
–	EXCEPTION: IF not all IP address information was allocated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent in step 7 THEN IF pc_S1_U_DataTransfer THEN In parallel to the event described in step 14b1 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 [18] subclause 4.5A.1 takes place performing IP address allocation in the U-plane. ELSE In parallel to the events described in step 8 below, the Generic ‘Procedure for IP address allocation in the CP CioT’ described in TS 36.508 [18], clause 8.1.5A.1 takes place.	–	–	–	–
8	Check: Does the UE transmit an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS bearer?	–>	ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT	1	P
9	Void
10	The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message included in an RRCConnectionReconfiguration message for the EPS bearer activated in steps 9B and 10.	<–	DEACTIVATE EPS BEARER CONTEXT REQUEST	–	–
11	The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.	–>	DEACTIVATE EPS BEARER CONTEXT ACCEPT	–	–
12	The SS releases the RRC connection.	–	–	–	–
13	Cause the UE to request connectivity to an additional PDN (see Note)	–	–	–	–
14	The UE transmits an RRCConnectionRequest-NB message with establishment cause set to “delayTolerantAccess-v1330”	–>	RRCConnectionRequest-NB	–	–
15a1	IF pc_S1_U_DataTransfer AND pc_NB_MultiDRB THEN The UE transmits a CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST	–	–
15a2	The SS establishes DRB associated with the default EPS bearer context activated during the preamble (a first PDN obtained during the attach procedure).	–	–	–	–
15a3	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
15a4	The UE transmit a PDN CONNECTIVITY REQUEST as specified to request an additional PDN.	–>	PDN CONNECTIVITY REQUEST	–	–
15b1	ELSE The UE transmit a CONTROL PLANE SERVICE REQUEST.	–>	CONTROL PLANE SERVICE REQUEST	–	–
15b2	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
15b3	The UE transmit a PDN CONNECTIVITY REQUEST as specified to request an additional PDN.	–>	PDN CONNECTIVITY REQUEST	–	–
16	The SS transmits a PDN CONNECTIVITY REJECT message with cause 26 “insufficient resources” and “T3396 value” included	<–	PDN CONNECTIVITY REJECT	–	–
17	The SS releases the RRC connection.	–	–	–	–
18	Cause the UE to request connectivity to the same PDN as used in step 1, with the NAS signalling low priority indicator set to indicate normal priority (see Note).	–	–	–	–
19a1	IF pc_S1_U_DataTransfer AND pc_NB_MultiDRB THEN The UE transmits a CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST	–	–
19a2	The SS establishes DRB associated with the default EPS bearer context activated during the preamble (a first PDN obtained during the attach procedure).	–	–	–	–
19a3	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
19a4	Check: Does the UE transmit a PDN CONNECTIVITY REQUEST as specified to request an additional PDN before the time indicated by timer T3396 has passed?	–>	PDN CONNECTIVITY REQUEST	2	P
19b1	ELSE The UE transmits a CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST PDN CONNECTIVITY REQUEST	2	P
19b2	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
19b3	Check: Does the UE transmit a PDN CONNECTIVITY REQUEST message before the time indicated by timer T3396 has passed??	–>	PDN CONNECTIVITY REQUEST	2	P
20	The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context.	<–	ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST	–	–
–	EXCEPTION: IF not all IP address information was allocated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent in step 7 THEN IF pc_S1_U_DataTransfer THEN In parallel to the event described in step 14b1 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 [18] subclause 4.5A.1 takes place performing IP address allocation in the U-plane. ELSE In parallel to the events described in step 14b1 below the Generic ‘Procedure for IP address allocation in the CP CioT’ described in TS 36.508 [18], clause 8.1.5A.1 takes place.	–	–	–	–
21	The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS bearer	–>	ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT	–	–
22	Void
23	The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message included in an RRCConnectionReconfiguration message for the EPS bearer activated in steps 9B and 10.	<–	DEACTIVATE EPS BEARER CONTEXT REQUEST	–	–
24	The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.	–>	DEACTIVATE EPS BEARER CONTEXT ACCEPT	–	–
25	The SS releases the RRC connection.	–	–	–	–
26	Cause the UE to request connectivity to an additional PDN (see Note)	–	–	–	–
27	The UE transmits an RRCConnectionRequest-NB message with establishment cause set to “delayTolerantAccess-v1330”	–>	RRCConnectionRequest-NB	–	–
28	The UE transmits a CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST	–	–
29	The SS transmits a SERVICE REJECT message with cause 22 “Congestion” and “T3346 value” included	<–	SERVICE REJECT	–	–
30	The SS releases the RRC connection.	–	–	–	–
31	Cause the UE to request connectivity to the same PDN as used in step 1, with the NAS signalling low priority indicator set to indicate normal priority (see Note).	–	–	–	–
32a1	IF pc_S1_U_DataTransfer AND pc_NB_MultiDRB THEN The UE transmits a CONTROL PLANE SERVICE REQUEST	–>	CONTROL PLANE SERVICE REQUEST	–	–
32a2	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
32a2	The SS establishes DRB associated with the default EPS bearer context activated during the preamble (a first PDN obtained during the attach procedure).	–	–	–	–
32a3	Check: Does the UE transmit a PDN CONNECTIVITY REQUEST as specified to request an additional PDN before the time indicated by timer T3346 has passed??	–>	PDN CONNECTIVITY REQUEST	3	P
32b1	ELSE The UE transmit a CONTROL PLANE SERVICE REQUEST.	–>	CONTROL PLANE SERVICE REQUEST	3	P
32b2	The SS transmits a SERVICE ACCEPT message	<–	SERVICE ACCEPT	–	–
32b3	Check: Does the UE transmit a PDN CONNECTIVITY REQUEST message before the time indicated by timer T3346 has passed??	–>	PDN CONNECTIVITY REQUEST	3	P
33	The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context.	<–	ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST	–	–
–	EXCEPTION: IF not all IP address information was allocated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent in step 7 THEN IF pc_S1_U_DataTransfer THEN In parallel to the event described in step 14b1 below the generic procedure for IP address allocation in the U-plane specified in TS 36.508 [18] subclause 4.5A.1 takes place performing IP address allocation in the U-plane. ELSE In parallel to the events described in step 14b1 below the Generic ‘Procedure for IP address allocation in the CP CioT’ described in TS 36.508 [18], clause 8.1.5A.1 takes place.	–	–	–	–
34	The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS bearer	–>	ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT	–	–
35	Void
36	The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message included in an RRCConnectionReconfiguration message for the EPS bearer activated in steps 9B and 10.	<–	DEACTIVATE EPS BEARER CONTEXT REQUEST	–	–
37	The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.	–>	DEACTIVATE EPS BEARER CONTEXT ACCEPT	–	–
38	The SS releases the RRC connection.	–	–	–	–
Note: The trigger in steps 1, 5, 12, 17, 24 and 29 is the same as in the generic procedure in 36.508 clause 6.4.3.2. The request of connectivity to an additional PDN may be performed by MMI or AT command.

22.6.5.3.3 Specific message contents

Table 22.6.5.3.3-1: Message ATTACH REQUEST (Preamble)

Derivation path: TS 36.508 table 4.7.2.-4
Information Element	Value/Remark	Comment	Condition
Device properties	1	“MS is configured for NAS signalling low priority”

Table 22.6.5.3.3-2: Void

Table 22.6.5.3.3-3: Message PDN CONNECTIVITY REQUEST (step 2a3 and 2a1, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	UE assigns a particular PTI not yet used between 1 and 254
ESM information transfer flag	Not present	This IE is only activable during an attach procedure.
Access point name	APN-1(New PDN name)	The requested PDN is different from default PDN

Table 22.6.5.3.3-4: Message PDN CONNECTIVITY REJECT (step 3, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-19
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	The SS indicates the same value like received in the PDN CONNECTIVITY REQUEST
ESM cause	01101111	“Protocol error, unspecified”
Extended protocol configuration options	Not present

Table 22.6.5.3.3-5: Message PDN CONNECTIVITY REQUEST (step 6a3 and 6b1, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-2	UE assigns a particular PTI not yet used between 1 and 254 (may be identical to PTI-1)
ESM information transfer flag	Not present	This IE is only activable during an attach procedure.
Access point name	APN-2 (New PDN name)	The requested PDN is different from default PDN (may be identical to APN-1)

Table 22.6.5.3.3-6: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 7, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-6 and table 4.6.1-8 with condition AM-DRB-ADD(2)
Information Element	Value/remark	Comment	Condition
EPS bearer identity	6
Procedure transaction identity	PTI-2	SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure.
Access point name	APN-2	SS re-uses the particular APN defined by UE for this present additional PDN connectivity request procedure

Table 22.6.5.3.3-7: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 8, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.3-1
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	6	Same value as in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST
Procedure transaction identity	0	"No procedure transaction identity assigned"

Table 22.6.5.3.3-8: Message RRCConnectionRequest-NB (step 14, Table 22.6.5.3.2-1)

Derivation path: TS 36.508 [18], table 8.1.6.1-10
Information Element	Value/Remark	Comment	Condition
RRCConnectionRequest-NB ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r13 SEQUENCE {
establishmentCause-r13	delayTolerantAccess-v1330
}
}
}

Table 22.6.5.3.3-9: Message CONTROL PLANE SERVICE REQUEST (step 15a1, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.2-28
Information Element	Value/remark	Comment	Condition
Device properties	1	‘MS is configured for NAS signalling low priority’

Table 22.6.5.3.3-10: Message CONTROL PLANE SERVICE REQUEST (step 15b1, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.2-28
Information Element	Value/remark	Comment	Condition
Device properties	1	‘MS is configured for NAS signalling low priority’

Table 22.6.5.3.3-11: Message PDN CONNECTIVITY REQUEST (step 15a3 and step 15b1, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	UE assigns a particular PTI not yet used between 1 and 254
ESM information transfer flag	Not present	This IE is only activable during an attach procedure.
Access point name	APN-1(New PDN name)	The requested PDN is different from default PDN
Device properties	1	‘MS is configured for NAS signalling low priority’

Table 22.6.5.3.3-12: Message PDN CONNECTIVITY REJECT (step 16, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-19
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	The SS indicates the same value like received in the PDN CONNECTIVITY REQUEST
ESM cause	00011010	#26 “insufficient resources”
T3396 value	1010 0101	5 minutes

Table 22.6.5.3.3-13: Message CONTROL PLANE SERVICE REQUEST (step 19a1, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.2-28
Information Element	Value/remark	Comment	Condition
Device properties	0	‘MS is not configured for NAS signalling low priority’

Table 22.6.5.3.3-14: Message CONTROL PLANE SERVICE REQUEST (step 19b1, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.2-28
Information Element	Value/remark	Comment	Condition
Device properties	0	‘MS is not configured for NAS signalling low priority’

Table 22.6.5.3.3-15: Message PDN CONNECTIVITY REQUEST (step 19a3 and step 19b1, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	UE assigns a particular PTI not yet used between 1 and 254
ESM information transfer flag	Not present	This IE is only activable during an attach procedure.
Access point name	APN-1(New PDN name)	The requested PDN is the same as in step 4
Device properties	0	‘MS is not configured for NAS signalling low priority’

Table 22.6.5.3.3-16: Message RRCConnectionRequest-NB (step 27, Table 22.6.5.3.2-1)

Derivation path: TS 36.508 [18], table 8.1.6.1-10
Information Element	Value/Remark	Comment	Condition
RRCConnectionRequest-NB ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r13 SEQUENCE {
establishmentCause-r13	delayTolerantAccess-v1330
}
}
}

Table 22.6.5.3.3-17: Message CONTROL PLANE SERVICE REQUEST (step 28a1, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.2-28
Information Element	Value/remark	Comment	Condition
Device properties	1	‘MS is configured for NAS signalling low priority’

Table 22.6.5.3.3-18: Message CONTROL PLANE SERVICE REQUEST (step 28b1, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.2-28
Information Element	Value/remark	Comment	Condition
Device properties	1	‘MS is configured for NAS signalling low priority’

Table 22.6.5.3.3-19: Message PDN CONNECTIVITY REQUEST (step 28b1, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	UE assigns a particular PTI not yet used between 1 and 254
ESM information transfer flag	Not present	This IE is only activable during an attach procedure.
Access point name	APN-1(New PDN name)	The requested PDN is different from default PDN
Device properties	1	‘MS is configured for NAS signalling low priority’

Table 22.6.5.3.3-20: Message SERVICE REJECT (step 28, table 22.6.5.3.2-1)

Derivation Path: 36.508 table 4.7.2-22
Information Element	Value/remark	Comment	Condition
EMM cause	0001 0110	#22 Congestion
T3346 value	0010 0101	5 minutes

Table 22.6.5.3.3-21: Message CONTROL PLANE SERVICE REQUEST (step 31a1, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.2-28
Information Element	Value/remark	Comment	Condition
Device properties	0	‘MS is not configured for NAS signalling low priority’

Table 22.6.5.3.3-22: Message CONTROL PLANE SERVICE REQUEST (step 31b1, table 22.6.5.3.2-1)

Derivation path: 36.508 table 4.7.2-28
Information Element	Value/remark	Comment	Condition
Device properties	0	‘MS is not configured for NAS signalling low priority’

Table 22.6.5.3.3-23: Message PDN CONNECTIVITY REQUEST (step 32a3 and step 32b1, table 22.6.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-20
Information Element	Value/remark	Comment	Condition
EPS bearer identity	0000	No EPS bearer identity assigned
Procedure transaction identity	PTI-1	UE assigns a particular PTI not yet used between 1 and 254
ESM information transfer flag	Not present	This IE is only activable during an attach procedure.
Access point name	APN-1(New PDN name)	The requested PDN is the same as in step 4
Device properties	0	‘MS is not configured for NAS signalling low priority’