10.9 UE routing of uplink packets

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

10.9.1 UE routing of uplink packets

10.9.1.1 Test Purpose (TP)

(1)

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

ensure that {

when { 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 dedicated EPS bearers }

then { UE evaluates the packet filters in the correct evaluation order and transmits IP packets in uplink on the dedicated EPS bearer associated with the matched packet filter }

}

(2)

with { the UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-CONNECTED mode with a default EPS bearer and two dedicated EPS bearers 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 configured in the UL TFT for the dedicated EPS bearers 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 state and in EMM-CONNECTED mode with a default EPS bearer and two dedicated EPS bearers active }

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 bearers }

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

}

(4)

with { the UE is in BEARER CONTEXT ACTIVE STATE state and in EMM-CONNECTED mode with a default EPS bearer and two dedicated EPS bearers 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 and dedicated EPS bearers }

then { the UE discards the IP packet }

}

10.9.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 23.060, clause 15.3.2.0 and TS 24.008, clause 10.5.6.12.

[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 the same direction (downlink or uplink) 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 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 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 apply for both directions. The packet filters determine the traffic mapping to PDP contexts. The downlink packet filters shall be applied by the network and the uplink packet filters shall be applied by the MS. A packet filter that applies for both directions shall be applied by the network as a downlink packet filter and by the MS as an uplink 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, 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. However, using "Add packet filters to existing TFT", it’s possible to create a TFT 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.

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
	Packet filter identifier 1	Octet 4
	Packet filter identifier 2	Octet 5
	…
	Packet filter identifier N	Octet N+3

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
Packet filter identifier 1								Octet 4
Packet filter evaluation precedence 1								Octet 5
Length of Packet filter contents 1								Octet 6
Packet filter contents 1								Octet 7 Octet m
Packet filter identifier 2								Octet m+1
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
Packet filter identifier N								Octet y+1
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 16.

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 1 0 0 0 0 0 IPv6 remote address 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.

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 "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 "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 to identify one or more packet filters in a TFT when modifying the QoS of a PDP context without modifying the packet filter itself.

10.9.1.3 Test description

10.9.1.3.1 Pre-test conditions

System Simulator:

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

UE:

– None.

Preamble:

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

10.9.1.3.2 Test procedure sequence

Table 10.9.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

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.

DRB3

(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.

DRB3

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 cl 15.3.3.3

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

DRB3

–

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 10.9.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	DRB2	Type I	All Type I packet filter components match	The IP packet is only matching Packet Filter 1 and 2 in Table 10.9.1.3.2-1. The IP packet is returned on DRB2 as Packet Filter 1 is evaluated before Packet Filter 2.
2	IP packet#2	DRB1	Type I	Remote Address does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
3	IP packet#3	DRB1	Type I	Protocol identifier/Next header does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
4	IP packet#4	DRB3	Type I	Single local port does not match	The IP packet is only matching Packet Filter 2 in Table 10.9.1.3.2-1. The IP packet is returned on DRB3.
5	IP packet#5	DRB1	Type I	Local port range does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
6	IP packet#6	DRB2	Type I	Single remote port does not match	IP packet is only matching Packet Filter 1 in Table 10.9.1.3.2-1. The IP packet is returned on DRB2.
7	IP packet#7	DRB1	Type I	Remote port range does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
8	IP packet#8	DRB1	Type I	Type of service/Traffic class does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
9	IP packet#9	DRB3	Type II	All Type II packet filter components match	The IP packet is only matching Packet Filter 3 in Table 10.9.1.3.2-1. The IP packet is returned on DRB3.
10	IP packet#10	DRB1	Type II	Remote Address does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
11	IP packet#11	DRB1	Type II	Protocol identifier/Next header does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
12	IP packet#12	DRB1	Type II	Security parameter index does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
13	IP packet#13	DRB1	Type II	Type of service/Traffic class does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
14	IP packet#14	DRB3	Type III	All Type III packet filter components match	The IP packet is only matching Packet Filter 4 in Table 10.9.1.3.2-1. The IP packet is returned on DRB2.
15	IP packet#15	DRB1	Type III	Remote Address does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
16	IP packet#16	DRB1	Type III	Type of service/Traffic class does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
17	IP packet#17	DRB1	Type III	Flow Label does not match	No packet filter matches. The IP packet is returned on DRB1 (default bearer)
18	IP packet#18	DRB1	Type I	Remote Address match	IP packet is only matching Packet Filter 5 in Table 10.9.1.3.2-1.
19	IP packet#19	None	Type I	Remote Address does not match	IP packet does not match any Packet Filters.
Note 1: IP Packet details are specified in Tables 10.9.1.3.3-5 to 10.9.1.3.3-14 in clause 10.9.1.3.3. Note 2: IP packets for sub-test index 1 to 17 are sent by the SS while no TFT is assigned to the default EPS bearer (associated by DRB1). IP packets for sub-test index 18 and 19 are sent by the SS after adding a TFT to the default EPS bearer.

The test procedure in Table 10.9.1.3.2-3 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 10.9.1.3.2-2a.

Table 10.9.1.3.2-2a: 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 10.9.1.3.2-3: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS performs the generic procedure to get UE in Loopback Activated (state 4) on Cell A establishing a default EPS bearer in accordance to Reference default EPS bearer context #1 (DRB1) as specified in subclause 6.6.1 in [18] and two dedicated EPS bearers (DRB2 and DRB3) with EPS bearer context as specified in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message for DRB2 and DRB3 in subclause 10.9.1.3.3.	–	–	–	–
	EXCEPTION: IF IPtype=’IPv4′ then test steps 1 to 2 are repeated for N= 1 to 13 using the IPv4 packet filters components in Table 10.9.1.3.2-1. IF IPtype=’IPv6′ then test steps 1 to 2 are repeated for N= 1 to 17 using the IPv6 packet filters components in Table 10.9.1.3.2-1.	–	–	–	–
1	The SS transmits one IP Packet according to Table 10.9.1.3.2-2 for Sub-test index=N on DRB1	–	–	–	–
2	Check: Does UE send the IP Packet on the data radio bearer as specified by Table 10.9.1.3.2-2 for Sub-test index=N?	–	–	1,2	P
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 message.	<–	MODIFY EPS BEARER CONTEXT REQUEST	–	–
4	UE transmits a MODIFY EPS BEARER CONTEXT ACCEPT message	–>	MODIFY EPS BEARER CONTEXT ACCEPT	–	–
5	The SS transmits one IP Packet according to Table 10.9.1.3.2-2 for Sub-test index=18 on DRB1	–	–	–	–
6	Check: Does UE send the IP Packet on the data radio bearer as specified by Table 10.9.1.3.2-2 for Sub-test index=18?	–	–	3	P
7	The SS transmits one IP Packet according to Table 10.9.1.3.2-2 for Sub-test index=19 on DRB1	–	–	–	–
8	Check: Does UE send an IP Packet on any of the dedicated or default data radio bearers?	–	–	4	F
–	EXCEPTION: Steps 9 – 18 are executed only if two executions apply and this is the first execution.	–	–	–	–
9	The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode.	<–	RRC: DLInformationTransfer TC: OPEN UE TEST LOOP	–	–
10	The UE transmits an OPEN UE TEST LOOP COMPLETE message.	–>	RRC: ULInformationTransfer 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 TC: DEACTIVATE TEST MODE	–	–
12	The UE transmits an DEACTIVATE TEST MODE COMPLETE message.	–>	RRC: ULInformationTransfer TC: DEACTIVATE TEST MODE COMPLETE	–	–
13	Void	–	–	–	–
14	Void	–	–	–	–
15	Void	–	–	–	–
16	Void	–	–	–	–
17	The UE is switched OFF. See Note.	–	–	–	–
18	The UE is switched ON.	–	–	–	–
Note: This implies detaching of the UE, releasing of the RRC connection and resetting of the radio bearers at the SS side.

10.9.1.3.3 Specific message contents

Table 10.9.1.3.3-0A: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Test execution 2: step 0, Table 10.9.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"
NOTE: IF MULTI_PDN according to the definition in TS 36.508 clause 4.5.2 [18] THEN the above IE values apply for the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST messages sent from the SS in step 16 and step 18c2 of the UE registration with test mode activation procedure acc. to TS 36.508 clause 4.5.2A.3-1 [18].

Table 10.9.1.3.3-0B: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (Test execution 1: step 0, Table 10.9.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"
NOTE: IF MULTI_PDN according to the definition in TS 36.508 clause 4.5.2 [18] THEN the above IE values apply for the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST messages sent from the SS in step 16 and step 18c2 of the UE registration with test mode activation procedure acc. to TS 36.508 clause 4.5.2A.3-1 [18].

Table 10.9.1.3.3-1: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST step 0, Table 10.9.1.3.2-3 (, DRB2)

Derivation path: 36.508 table 4.7.3-3 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	0	"No procedure transaction identity assigned"
Linked EPS bearer identity	5	SS re-uses the EPS bearer identity of the default EPS bearer context.
EPS QoS	According to reference dedicated EPS bearer context #1 – see [18]
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 10.9.1.3.2-1.

Table 10.9.1.3.3-2: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST ( step 0, Table 10.9.1.3.2-3, DRB3)

Derivation path: 36.508 table 4.7.3-3 and table 4.6.1-8 with condition AM-DRB-ADD(3)
Information Element	Value/Remark	Comment	Condition
EPS bearer identity	7
Procedure transaction identity	0	"No procedure transaction identity assigned"
Linked EPS bearer identity	5	SS re-uses the EPS bearer identity of the default EPS bearer context.
EPS QoS	According to reference dedicated EPS bearer context #1 – see [18]
TFT
TFT operation code	"create new TFT"
E bit	0
Packet filters (Note 1)	2, 3		IPv4
	2, 3, 4		IPv6
Note 1: This row refers to the packet filters defined in Table 10.9.1.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 10.9.1.3.3-3: Message MODIFY EPS BEARER CONTEXT REQUEST (step 3, Table 10.9.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)	5	SS adds packet filter to the default EPS bearer context.
Note 1: This row refers to the packet filters defined in Table 10.9.1.3.2-1.

Table 10.9.1.3.3-4: Message MODIFY EPS BEARER CONTEXT ACCEPT (step 4, Table 10.9.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 10.9.1.3.3-4A: Void

Table 10.9.1.3.3-5: IP packet#1 (Table 10.9.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 10.9.1.3.3-6: IP packet#2 (Table 10.9.1.3.2-2)

Derivation path: IP packet#1, Table 10.9.1.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 10.9.1.3.3-7: IP packet#3 (Table 10.9.1.3.2-2)

Derivation path: IP packet#1, Table 10.9.1.3.3-5

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 10.9.1.3.3-8: IP packet#4 (Table 10.9.1.3.2-2)

Derivation path: IP packet#1, Table 10.9.1.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 10.9.1.3.3-9: IP packet#5 (Table 10.9.1.3.2-2)

Derivation path: IP packet#1, Table 10.9.1.3.3-5
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 10.9.1.3.3-10: IP packet#6 (Table 10.9.1.3.2-2)

Derivation path: IP packet#1, Table 10.9.1.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 10.9.1.3.3-11: IP packet#7 (Table 10.9.1.3.2-2)

Derivation path: IP packet#1, Table 10.9.1.3.3-5
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 10.9.1.3.3-12: IP packet#8 (Table 10.9.1.3.2-2)

Derivation path: IP packet#1, Table 10.9.1.3.3-5
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 10.9.1.3.3-13: IP packet#9 (Table 10.9.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 10.9.1.3.3-14: IP packet#10 (Table 10.9.1.3.2-2)

Derivation path: IP packet#9, Table 10.9.1.3.3-13
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 10.9.1.3.3-15: IP packet#11 (Table 10.9.1.3.2-2)

Derivation path: IP packet#9, Table 10.9.1.3.3-13

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 10.9.1.3.3-16: IP packet#12 (Table 10.9.1.3.2-2)

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

Table 10.9.1.3.3-17: IP packet#13 (Table 10.9.1.3.2-2)

Derivation path: IP packet#9, Table 10.9.1.3.3-13
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 10.9.1.3.3-18: IP packet#14 (Table 10.9.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 10.9.1.3.3-19: IP packet#15 (Table 10.9.1.3.2-2)

Derivation path: IP packet#14, Table 10.9.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 10.9.1.3.3-20: IP packet#16 (Table 10.9.1.3.2-2)

Derivation path: IP packet#14, Table 10.9.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 10.9.1.3.3-21: IP packet#17 (Table 10.9.1.3.2-2)

Derivation path: IP packet#14, Table 10.9.1.3.3-18

Information Element

Value/Remark

Comment

Condition

Flow Label

IPv6

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

Table 10.9.1.3.3-22: IP packet#18 (Table 10.9.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 10.9.1.3.3-23: IP packet#19 (Table 10.9.1.3.2-2)

Derivation path: IP packet#18, Table 10.9.1.3.3-22
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