10.8 UE requested bearer resource modification

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

10.8.1 UE requested bearer resource modification accepted by the network / New EPS bearer context

10.8.1.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 dedicated 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 an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message with the procedure transaction identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message }

then { UE sends an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message }

}

10.8.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 6.4.2.3, 6.5.4.2 and 6.5.4.3.

[TS 24.301, clause 6.4.2.3]

The linked EPS bearer identity included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message indicates to the UE to which default bearer, IP address and PDN the dedicated bearer is linked.

If the PTI is included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, 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 dedicated bearer context activation is related.

[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.3.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.

Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST, MODIFY EPS BEARER CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST with a PTI which matches the value used for the BEARER RESOURCE MODIFICATION REQUEST, the UE shall stop timer T3481 and enter the state PROCEDURE TRANSACTION INACTIVE.

i) If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST is received, the UE shall verify that the EPS bearer identity given in the EPS bearer identity IE is not already used by any dedicated EPS bearer contexts associated with the included linked EPS bearer identity. The UE shall then proceed as described in subclause 6.4.2.3 or subclause 6.4.2.4.

10.8.1.3 Test description

10.8.1.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

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

– A default EPS bearer and a dedicated bearer are established between the first PDN and the UE.

10.8.1.3.2 Test procedure sequence

Table 10.8.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause the UE to request bearer resource modification of dedicated EPS bearer associated with first PDN connectivity.(see Note)

2

Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?

–>

BEARER RESOURCE MODIFICATION REQUEST

1

P

3

The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.

<–

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

4

Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message?

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

2

P

Note: The trigger in step 1 and the RRC messages in steps 2 to 4 are the same as in the generic procedure in 36.508 clause 6.4.3.3.

10.8.1.3.3 Specific message contents

Table 10.8.1.3.3-1: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 3, Table 10.8.1.3.2-1)

Derivation path: 36.508 table 4.7.3-3, condition UE-INITIATED and table 4.6.1-8 with condition AM-DRB-ADD(3)

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

7

EPS QoS

According to reference dedicated EPS bearer context #1 – see [18]

TFT

According to reference dedicated EPS bearer context #2 – see [18]

10.8.2 UE requested bearer resource modification accepted by the network / Existing EPS bearer context

10.8.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 dedicated 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 }

}

10.8.2.2 Conformance requirements

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

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

Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST, MODIFY EPS BEARER CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST message with a PTI which matches the value used for the BEARER RESOURCE MODIFICATION REQUEST message, the UE shall stop timer T3481 and enter the state PROCEDURE TRANSACTION INACTIVE.

ii) 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.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.

10.8.2.3 Test description

10.8.2.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None

Preamble:

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

– A default EPS bearer and a dedicated bearer are established between the first PDN and the UE.

10.8.2.3.2 Test procedure sequence

Table 10.8.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 dedicated EPS bearer associated with first PDN connectivity.(see Note)

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: The trigger in step 1 and the RRC messages in steps 2 to 4 are the same as in the generic procedure in 36.508 clause 6.4.3.3.

10.8.2.3.3 Specific message contents

Table 10.8.2.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, Table 10.8.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

6

Table 10.8.2.3.3-2: Message MODIFY EPS BEARER CONTEXT REQUEST (step 3, Table 10.8.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

6

New EPS QoS

According to reference dedicated EPS bearer context #1 – see [18]

10.8.3 UE requested bearer resource modification not accepted by the network

10.8.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 }

}

10.8.3.2 Conformance requirements

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

[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; 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.

The further actions to be performed by the UE are implementation dependent as part of upper layers responsibility.

[TS 24.301, clause 7.3.1]

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

h) If the UE receives an ACTIVATE DEDICATED 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 an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message including ESM cause #47 "PTI mismatch".

10.8.3.3 Test description

10.8.3.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

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

– A default EPS bearer and a dedicated bearer are established between the first PDN and the UE.

10.8.3.3.2 Test procedure sequence

Table 10.8.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 dedicated EPS bearer associated with first PDN connectivity.(see Note 1)

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

3A

SS waits for 500ms (Note 2).

4

The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.

<–

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

5

Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message?

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT

1

P

Note 1: The trigger in step 1 and the RRC messages in steps 2 to 5 are the same as in the generic procedure in 36.508 clause 6.4.3.3.

Note 2: The timer of 500ms is added to ensure that UE receives BEARER RESOURCE MODIFICATION REJECT message before ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message.

10.8.3.3.3 Specific message contents

Table 10.8.3.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, Table 10.8.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

6

Table 10.8.3.3.3-2: Message BEARER RESOURCE MODIFICATION REJECT (step 3, Table 10.8.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 10.8.3.3.3-3: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 4, Table 10.8.3.3.2-1)

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

The same value as the value set in BEARER RESOURCE MODIFICATION REQUEST message in step 2.

Linked EPS bearer identity

5

EPS QoS

According to reference dedicated EPS bearer context #2 – see [18]

TFT

According to reference dedicated EPS bearer context #2 – see [18]

Table 10.8.3.3.3-4: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT (step 5, Table 10.8.3.3.2-1)

Derivation path: 36.508 table 4.7.3-2

Information Element

Value/Remark

Comment

Condition

ESM cause

‘0010 1111’B

PTI mismatch

10.8.4 UE requested bearer resource modification / Cause #36 "regular deactivation"

10.8.4.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE is requested to release of bearer resources corresponding to the dedicated bearer }

then { UE sends a BEARER RESOURCE MODIFICATION REQUEST message with a cause “regular deactivation” }

}

(2)

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

ensure that {
when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message with the procedure transaction identity (PTI) indicated in the BEARER RESOURCE MODIFICATION REQUEST message and the EPS bearer identity pointing an existing EPS bearer context }

then { UE deactivates the EPS bearer context identified by the EPS bearer identity indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST message and sends a DEACTIVATE EPS BEARER CONTEXT ACCEPT message }

}

10.8.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 6.5.4.3, 6.4.4.3 and 7.3.2.

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

Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST, MODIFY EPS BEARER CONTEXT REQUEST or DEACTIVATE EPS BEARER CONTEXT REQUEST message with a PTI which matches the value used for the BEARER RESOURCE MODIFICATION REQUEST message, the UE shall stop timer T3481 and enter the state PROCEDURE TRANSACTION INACTIVE.

iii) If the DEACTIVATE 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 associated with the included linked EPS bearer identity The UE shall then proceed as described in subclause 6.4.4.3.

[TS 24.301, clause 6.4.4.3]

Upon receipt of the DEACTIVATE EPS BEARER CONTEXT REQUEST message, the UE shall delete the EPS bearer context identified by the EPS bearer identity. After deactivating the identified EPS bearer context, the UE shall respond to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT.

Upon sending the DEACTIVATE EPS BEARER CONTEXT ACCEPT message, the UE shall enter the state BEARER CONTEXT INACTIVE

If the DEACTIVATE 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 modification procedure or UE requested PDN disconnect procedure to which the EPS bearer context deactivation is related (see subclause 6.5.4).

If the DEACTIVATE 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 shall release the traffic flow aggregate description associated to the PTI value provided.

[TS 24.301, clause 7.3.2]

The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen EPS bearer identity received in the header of an ESM message:

i) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message which includes an unassigned or reserved EPS bearer identity value or an assigned EPS bearer identity value that does not match an existing EPS bearer context, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including ESM cause #43 "invalid EPS bearer identity".

10.8.4.3 Test description

10.8.4.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

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

– A default EPS bearer and a dedicated bearer are established between the first PDN and the UE.

10.8.4.3.2 Test procedure sequence

Table 10.8.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause the UE to request bearer resource release of dedicated EPS bearer associated with first PDN connectivity (see Note).

2

Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?

–>

BEARER RESOURCE MODIFICATION REQUEST

1

P

3

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message.

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

4

Check: Does the UE transmit a DEACTIVATE EPS BEARER CONTEXT ACCEPT message?

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

2

P

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

2

P

Note: The trigger in step 1 and the RRC messages in steps 2 to 4 are the same as in the generic procedure in 36.508 clause 6.4.3.4.

10.8.4.3.3 Specific message contents

Table 10.8.4.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, Table 10.8.4.3.2-1)

Derivation path: 36.508 table 4.7.3-8, condition RELEASE-REQUESTED

Information Element

Value/Remark

Comment

Condition

EPS bearer identity for packet filter

6

ESM cause

‘0010 0100’B

Regular deactivation

Table 10.8.4.3.3-2: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 3, Table 10.8.4.3.2-1)

Derivation path: 36.508 table 4.7.3-12, condition UE-INITIATED and table 4.6.1-8 with condition DRB-REL(2)

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Table 10.8.4.3.3-3: Message MODIFY EPS BEARER CONTEXT REQUEST (step 5, Table 10.8.4.3.2-1)

Derivation path: 36.508 table 4.7.3-18, condition NETWORK-INITIATED

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

New EPS QoS

According to reference dedicated EPS bearer context #2 – see [18]

TFT

According to reference dedicated EPS bearer context #2 except for TFT operation code – see [18]

TFT operation code

‘100’B

Replace packet filters in existing TFT

Table 10.8.4.3.3-4: Message MODIFY EPS BEARER CONTEXT REJECT (step 6, Table 10.8.4.3.2-1)

Derivation path: 36.508 table 4.7.3-17

Information Element

Value/Remark

Comment

Condition

ESM cause

‘0010 1011’B

Invalid EPS bearer identity

10.8.5 UE requested bearer resource modification / BEARER RESOURCE MODIFICATION REJECT message including cause #43 "invalid EPS bearer identity"

10.8.5.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 “invalid EPS bearer identity” }

then { UE deactivates the EPS bearer context identified by the EPS bearer identity indicated in the BEARER RESOURCE MODIFICATION REQUEST message }

}

10.8.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 6.5.4.4, 6.5.4.5 and 7.3.2.

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

#43: invalid EPS bearer identity;

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.

The further actions to be performed by the UE are implementation dependent as part of upper layers responsibility.

[TS 24.301, clause 6.5.4.5]

The following abnormal cases can be identified:

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.

[TS 24.301, clause 7.3.2]

The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen EPS bearer identity received in the header of an ESM message:

h) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message which includes an unassigned or reserved EPS bearer identity value or an assigned EPS bearer identity value that does not match an existing EPS bearer context, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including ESM cause #43 "invalid EPS bearer identity".

10.8.5.3 Test description

10.8.5.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

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

– A default EPS bearer and a dedicated bearer are established between the first PDN and the UE.

10.8.5.3.2 Test procedure sequence

Table 10.8.5.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause the UE to request bearer resource modification of dedicated EPS bearer associated with first PDN connectivity.(see Note)

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

The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message. This message is included in a DLInformationTransfer message.

<–

MODIFY EPS BEARER CONTEXT REQUEST

5

Check: Does the UE transmit a MODIFY EPS BEARER CONTEXT REJECT message?

–>

MODIFY EPS BEARER CONTEXT REJECT

1

P

Note: The trigger in step 1 and the RRC messages in steps 2 to 5 are the same as in the generic procedure in 36.508 clause 6.4.3.3.

10.8.5.3.3 Specific message contents

Table 10.8.5.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, Table 10.8.5.3.2-1)

Derivation path: 36.508 table 4.7.3-8

Information Element

Value/Remark

Comment

Condition

EPS bearer identity for packet filter

6

Table 10.8.5.3.3-2: Message BEARER RESOURCE MODIFICATION REJECT (step 3, Table 10.8.5.3.2-1)

Derivation path: 36.508 table 4.7.3-7

Information Element

Value/Remark

Comment

Condition

ESM cause

‘0010 1011’B

Invalid EPS bearer identity

Table 10.8.5.3.3-3: Message MODIFY EPS BEARER CONTEXT REQUEST (step 4, Table 10.8.5.3.2-1)

Derivation path: 36.508 table 4.7.3-18 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

New EPS QoS

According to reference dedicated EPS bearer context #2 – see [18]

TFT

According to reference dedicated EPS bearer context #2 except for TFT operation code – see [18]

TFT operation code

‘100’B

Replace packet filters in existing TFT

Table 10.8.5.3.3-4: Message MODIFY EPS BEARER CONTEXT REJECT (step 5, Table 10.8.5.3.2-1)

Derivation path: 36.508 table 4.7.3-17

Information Element

Value/Remark

Comment

Condition

ESM cause

‘0010 1011’B

Invalid EPS bearer identity

10.8.6 UE requested bearer resource modification / Collision of a UE requested bearer resource modification procedure and EPS bearer context deactivation procedure

10.8.6.1 Test Purpose (TP)

(1)

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

ensure that {
when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message with an unassigned PTI value and the EPS bearer identity indicated in the BEARER RESOURCE MODIFICATION REQUEST message }

then { UE aborts the UE requested bearer resource modification procedure and deactivates the EPS bearer context identified by the EPS bearer identity indicated in DEACTIVATE EPS BEARER CONTEXT REQUEST message and sends a DEACTIVATE EPS BEARER CONTEXT ACCEPT message }

}

10.8.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 6.5.4.5 and 7.3.2.

[TS 24.301, clause 6.5.4.5]

The following abnormal cases can be identified:

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 UE 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".

10.8.6.3 Test description

10.8.6.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

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

– A default EPS bearer and a dedicated bearer are established between the first PDN and the UE.

10.8.6.3.2 Test procedure sequence

Table 10.8.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause the UE to request bearer resource modification of dedicated EPS bearer associated with first PDN connectivity.(see Note)

2

The UE transmits a BEARER RESOURCE MODIFICATION REQUEST message.

–>

BEARER RESOURCE MODIFICATION REQUEST

3

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST message.

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

4

Check: Does the UE transmit a DEACTIVATE EPS BEARER CONTEXT ACCEPT message?

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

1

P

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

P

Note: The trigger in step 1 and the RRC messages in steps 2 to 4 are the same as in the generic procedure in 36.508 clause 6.4.3.4.

10.8.6.3.3 Specific message contents

Table 10.8.6.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, Table 10.8.6.3.2-1)

Derivation path: 36.508 table 4.7.3-8

Information Element

Value/Remark

Comment

Condition

EPS bearer identity for packet filter

6

Table 10.8.6.3.3-2: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 3, Table 10.8.6.3.2-1)

Derivation path: 36.508 table 4.7.3-12, condition NETWORK-INITIATED and table 4.6.1-8 with condition DRB-REL(2)

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Table 10.8.6.3.3-3: Message MODIFY EPS BEARER CONTEXT REQUEST (step 5, Table 10.8.6.3.2-1)

Derivation path: 36.508 table 4.7.3-18

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Procedure transaction identity

The same value as the value set in BEARER RESOURCE MODIFICATION REQUEST message in step 2.

New EPS QoS

According to reference dedicated EPS bearer context #2 – see [18]

TFT

According to reference dedicated EPS bearer context #2 except for TFT operation code – see [18]

TFT operation code

‘100’B

Replace packet filters in existing TFT

Table 10.8.6.3.3-4: Message MODIFY EPS BEARER CONTEXT REJECT (step 6, Table 10.8.6.3.2-1)

Derivation path: 36.508 table 4.7.3-17

Information Element

Value/Remark

Comment

Condition

ESM cause

‘0010 1111’B

PTI mismatch

10.8.7 UE requested bearer resource modification / Expiry of timer T3481

10.8.7.1 Test Purpose (TP)

(1)

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 }

}

(2)

with { UE is in EMM-REGISTERED.NO-CELL-AVAILABLE state and has deactivated the EPS bearer context without peer-to-peer signalling between the UE and the MME }

ensure that {
when { UE receives indication of "back to E-UTRAN coverage" from the lower layers }

then { UE sends TRACKING AREA UPDATE REQUEST message }

}

10.8.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.5.3.2.2 and 6.5.4.5.

[TS 24.301, clause 5.5.3.2.2]

The UE in state EMM-REGISTERED shall initiate the tracking area updating procedure by sending a TRACKING AREA UPDATE REQUEST message to the MME,

f) when the UE deactivated EPS bearer context(s) locally while in EMM-REGISTERED.NO-CELL-AVAILABLE, and then returns to EMM-REGISTERED.NORMAL-SERVICE;

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

10.8.7.3 Test description

10.8.7.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

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

– A default EPS bearer and a dedicated bearer are established between the first PDN and the UE.

– DRX is not configured

10.8.7.3.2 Test procedure sequence

Table 10.8.7.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Cause the UE to request bearer resource release of dedicated EPS bearer associated with first PDN connectivity.(see Note 1)

2

The UE transmits a BEARER RESOURCE MODIFICATION REQUEST message.

–>

BEARER RESOURCE MODIFICATION REQUEST

3

Wait for 8 s to ensure that T3481 expires (1st expiry).

(Note 2)

4

Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?

–>

BEARER RESOURCE MODIFICATION REQUEST

1

P

5

Wait for 8 s to ensure that T3481 expires (2nd expiry).

(Note 2)

6

Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?

–>

BEARER RESOURCE MODIFICATION REQUEST

1

P

7

Wait for 8 s to ensure that T3481 expires (3rd expiry).

(Note 2)

8

Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?

–>

BEARER RESOURCE MODIFICATION REQUEST

1

P

9

Wait for 8 s to ensure that T3481 expires (4th expiry).

(Note 2)

10

Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message?

–>

BEARER RESOURCE MODIFICATION REQUEST

1

P

11

Set the cell type of Cell A to the "Non-suitable “Off” cell".

12

Wait for 12 s to ensure that T310 plus T311 as well as T3481 expire (5th expiry).

(Note 3)

13

Set the cell type of Cell A to the "Suitable cell".

14

Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message?

–>

TRACKING AREA UPDATE REQUEST

2

P

15

The SS transmits a TRACKING AREA UPDATE ACCEPT message.

<–

TRACKING AREA UPDATE ACCEPT

16

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

–>

TRACKING AREA UPDATE COMPLETE

At the end of this test procedure sequence, the UE is in end state E-UTRA connected (E2_T3440) according to TS 36.508.

Note 1: The trigger in step 1 and the RRC messages in steps 2 to 10 are the same as in the generic procedure in 36.508 clause 6.4.3.3.

Note 2: If the UE supports CE mode B and UEs usage setting is not voice centric, T3481 takes a value of 16s (see TS 24.301 Table 10.3.1).

Note 3: If the UE supports CE mode B and UEs usage setting is not voice centric, wait period will be 16s.

10.8.7.3.3 Specific message contents

Table 10.8.7.3.3-1: Message BEARER RESOURCE MODIFICATION REQUEST (step 2, step 4, step 6, step 8 and step 10, Table 10.8.7.3.2-1)

Derivation path: 36.508 table 4.7.3-8, condition RELEASE-REQUESTED

Information Element

Value/Remark

Comment

Condition

EPS bearer identity for packet filter

6

Table 10.8.7.3.3-2: Message TRACKING AREA UPDATE REQUEST (step 14, Table 10.8.7.3.2-1)

Derivation path: 36.508 table 4.7.2-27

Information Element

Value/Remark

Comment

Condition

EPS bearer context status

EPS bearer context status IEI

57

Length of EPS bearer context status contents

2

2 octets

EBI(0)-EBI(4)

‘0 0000’B

EBI(5-7)

‘001’B

EBI(8)-EBI(15)

‘0000 0000’B

Table 10.8.7.3.3-3: Message TRACKING AREA UPDATE ACCEPT (step 15, Table 10.8.7.3.2-1)

Derivation path: 36.508 table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

EPS bearer context status

EPS bearer context status IEI

57

Length of EPS bearer context status contents

2

2 octets

EBI(0)-EBI(4)

‘0 0000’B

EBI(5-7)

‘001’B

EBI(8)-EBI(15)

‘0000 0000’B

Table 10.8.7.3.3-4: RRCConnectionReconfiguration (preamble)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

drx-Config

Not present

}

}

}

}

}

}

10.8.8 UE requested bearer resource modification / Dual priority / low priority override

10.8.8.1 Test Purpose (TP)

(1)

with { UE configured for low priority NAS signalling and low priority NAS signalling override }

ensure that {

when { UE is triggered to request connectivity to an additional PDN by overriding NAS signalling priority configured in UE }

then { the UE transmits a PDN CONNECTIVITY REQUEST message with the low priority indicator to "MS is not configured for NAS signalling low priority" }

}

(2)

with { UE configured for low priority NAS signalling and low priority NAS signalling override }

ensure that {

when { UE is requested to modify of bearer resource corresponding to the dedicated bearer previously established by overriding NAS signalling low priority }

then { UE sends a BEARER RESOURCE MODIFICATION REQUEST message with the low priority indicator to "MS is not configured for NAS signalling low priority"}

}

10.8.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 4.2.A

[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 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 accessing the network with access class 11 – 15; 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.

10.8.8.3 Test description

10.8.8.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

– UE is configured for low priority NAS signalling

– UE is configured for low priority NAS signalling override

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

Table 10.8.8.3.1-1: USIM Configuration

USIM field

Value

EFUST

Service 96 is supported.

EFNASCONFIG

“NAS_SignallingPriority is set to NAS signalling low priority” as defined in TS 24.368, clause 5.3.

EFNASCONFIG

“Override_NAS_SignallingLowPriority is set to UE can override the NAS signalling low priority indicator” as defined in TS 24.368, clause 5.9.

EFNASCONFIG

“ExtendedAccessBarring is set to extended access barring is applied for the UE” as defined in TS 24.368, clause 5.8

EFNASCONFIG

“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].10.5.1.3.2

10.8.8.3.2 Test procedure sequence

Table 10.8.8.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 with NAS Signalling Low Priority override (see Note1)

2

The UE transmits an RRCConnectionRequest message with establishmentCause set to ‘mo-Data’ followed by a SERVICE REQUEST message.

–>

SERVICE REQUEST

3

The SS establishes SRB2 and DRB associated with default EPS bearer context (a first PDN obtained during the attach procedure).

4

Check: Does the UE include the Device properties IE set to “MS is not configured for NAS signalling low priority”?

–>

PDN CONNECTIVITY REQUEST

1

P

5

The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE EPS Bearer Identity set to new EPS bearer context and ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message with IE Linked EPS bearer identity set to the new EPS bearer context.

Note:

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST and ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST are included in dedicatedInfoNASList of RRCConnectionReconfiguration message.

<–

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

EXCEPTION: In parallel to the event described in step 6 below, the generic procedure for IP address allocation in the U-plane specified in TS 36.508 subclause 4.5A.1 takes place performing IP address allocation in the U-plane.

EXCEPTION: In parallel with step 6 below, the test step in the parallel behaviour in table 10.8.8.3.2-2 is taking place

6

The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message for the additional default EPS Bearer.

–>

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

7

Cause the UE to request bearer resource modification of dedicated EPS bearer associated with second PDN connectivity.(see Note2)

8

Check: Does the UE transmit a BEARER RESOURCE MODIFICATION REQUEST message with the low priority indicator to "MS is not configured for NAS signalling low priority"?

–>

BEARER RESOURCE MODIFICATION REQUEST

2

P

9

The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message containingEPS Bearer ID of dedicated EPS bearer associated with second PDN connectivity.

<–

MODIFY EPS BEARER CONTEXT REQUEST

10

The UE transmits an MODIFY EPS BEARER CONTEXT ACCEPT message

–>

MODIFY EPS BEARER CONTEXT ACCEPT

Note 1: The request of connectivity to an additional PDN may be performed by MMI or AT command.

Note 2: The trigger in step 7 and the RRC messages in steps 8 to 10 are the same as in the generic procedure in 36.508 clause 6.4.3.3.

Table 10.8.8.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the dedicated EPS Bearer.

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

10.8.8.3.3 Specific message contents

Table 10.8.8.3.3-1: Message PDN CONNECTIVITY REQUEST (step 4, Table 10.8.8.3.2-1)

Derivation Path: TS 36.523 Table 10.5.1.3.3-1

Information Element

Value/remark

Comment

Condition

Device properties

0

MS is not configured for NAS signalling low priority

Table 10.8.8.3.3-2: Message BEARER RESOURCE MODIFICATION REQUEST (step 8, Table 10.8.8.3.2-1)

Derivation path: 36.508 table 4.7.3-8

Information Element

Value/Remark

Comment

Condition

Device properties

0

MS is not configured for NAS signalling low priority