10.7 UE requested bearer resource allocation

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

10.7.1 UE requested bearer resource allocation accepted by the network / New EPS bearer context

10.7.1.1 Test Purpose (TP)

(1)

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

ensure that {
when { UE is requested to allocate of bearer resource }

then { UE sends a BEARER RESOURCE ALLOCATION REQUEST message }

}

(2)

with { UE has sent the BEARER RESOURCE ALLOCATION 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 ALLOCATION REQUEST message }

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

}

10.7.1.2 Conformance requirements

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

[TS 24.301, clause 6.5.3.2]

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

The UE shall include the EPS bearer identity of the default EPS bearer associated with the requested bearer resource in the Linked EPS bearer identity IE. The UE shall set the TFT operation code in the Traffic flow aggregate IE to "Create new TFT". In the Required traffic flow QoS IE, the UE shall indicate a QCI and, if the UE also includes a GBR, the additional GBR required for the traffic flow aggregate.

…

[TS 24.301, clause 6.5.3.3]

…

If the bearer resource allocation requested is accepted by the network, the MME shall initiate either a dedicated EPS bearer context activation procedure or an EPS bearer context modification procedure. Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST with a PTI which matches the value used for the BEARER RESOURCE ALLOCATION REQUEST, the UE shall stop timer T3480 and enter the state PROCEDURE TRANSACTION INACTIVE.

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.7.1.3 Test description

10.7.1.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

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

10.7.1.3.2 Test procedure sequence

Table 10.7.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

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

–

–

–

–

2

The UE transmits a SERVICE REQUEST message.

–>

SERVICE REQUEST

–

–

2A

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

–

–

–

–

3

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

–>

BEARER RESOURCE ALLOCATION REQUEST

1

P

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 ACCEPT message?

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

2

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

10.7.1.3.3 Specific message contents

Table 10.7.1.3.3-1: Message BEARER RESOURCE ALLOCATION REQUEST (step 3, Table 10.7.1.3.2-1)

Derivation path: 36.508 table 4.7.3-6B

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

5

Table 10.7.1.3.3-2: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 4, Table 10.7.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(2)

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Linked EPS bearer identity

5

10.7.2 UE requested bearer resource allocation accepted by the network / Existing EPS bearer context

10.7.2.1 Test Purpose (TP)

(1)

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

ensure that {
when { UE is requested to allocate of bearer resource }

then { UE sends a BEARER RESOURCE ALLOCATION REQUEST message }

}

(2)

with { UE has sent a BEARER RESOURCE ALLOCATION 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 ALLOCATION REQUEST message }

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

}

10.7.2.2 Conformance requirements

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

[TS 24.301, clause 6.5.3.2]

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

The UE shall include the EPS bearer identity of the default EPS bearer associated with the requested bearer resource in the Linked EPS bearer identity IE. The UE shall set the TFT operation code in the Traffic flow aggregate IE to "Create new TFT". In the Required traffic flow QoS IE, the UE shall indicate a QCI and, if the UE also includes a GBR, the additional GBR required for the traffic flow aggregate.

…

[TS 24.301, clause 6.5.3.3]

…

If the bearer resource allocation requested is accepted by the network, the MME shall initiate either a dedicated EPS bearer context activation procedure or an EPS bearer context modification procedure. Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST with a PTI which matches the value used for the BEARER RESOURCE ALLOCATION REQUEST, the UE shall stop timer T3480 and enter the state PROCEDURE TRANSACTION INACTIVE.

…

If the MODIFY EPS BEARER CONTEXT REQUEST 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.

10.7.2.3 Test description

10.7.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.7.2.3.2 Test procedure sequence

Table 10.7.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

The SS releases the RRC connection.

–

–

–

–

1

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

–

–

–

–

2

The UE transmits a SERVICE REQUEST message.

–>

SERVICE REQUEST

–

–

2A

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

–

–

–

–

3

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

–>

BEARER RESOURCE ALLOCATION REQUEST

1

P

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 ACCEPT message?

–>

MODIFY EPS BEARER CONTEXT ACCEPT

2

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

10.7.2.3.3 Specific message contents

Table 10.7.2.3.3-1: Message BEARER RESOURCE ALLOCATION REQUEST (step 3, Table 10.7.2.3.2-1)

Derivation path: 36.508 table 4.7.3-6B

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

5

Table 10.7.2.3.3-2: Message MODIFY EPS BEARER CONTEXT REQUEST (step 4, Table 10.7.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]

TFT

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

SS modifies the current packet filters of the dedicated EPS bearer context.

TFT operation code

‘011’B

Add packet filters to existing TFT

10.7.3 UE requested bearer resource allocation not accepted by the network

10.7.3.1 Test Purpose (TP)

(1)

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

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

then { UE enters state PROCEDURE TRANSACTION INACTIVE }

}

10.7.3.2 Conformance requirements

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

[TS 24.301, clause 6.5.3.4]

If the bearer resource allocation requested cannot be accepted by the network, the MME shall send a BEARER RESOURCE ALLOCATION 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 allocation.

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 ALLOCATION REJECT message, the UE shall stop the timer T3480, release the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE TRANSACTION INACTIVE.

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.7.3.3 Test description

10.7.3.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

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

10.7.3.3.2 Test procedure sequence

Table 10.7.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

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

–

–

–

–

2

The UE transmits a SERVICE REQUEST message.

–>

SERVICE REQUEST

–

–

2A

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

–

–

–

–

3

The UE transmits a BEARER RESOURCE ALLOCATION REQUEST message.

–>

BEARER RESOURCE ALLOCATION REQUEST

–

–

4

The SS transmits a BEARER RESOURCE ALLOCATION REJECT message.

<–

BEARER RESOURCE ALLOCATION REJECT

–

–

4A

SS waits for 500ms (Note 2).

–

–

–

–

5

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

<–

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

–

6

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 6 are the same as in the generic procedure in 36.508 clause 6.4.3.1.

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

10.7.3.3.3 Specific message contents

Table 10.7.3.3.3-1: Message BEARER RESOURCE ALLOCATION REQUEST (step 3, Table 10.7.3.3.2-1)

Derivation path: 36.508 table 4.7.3-6B

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

5

Table 10.7.3.3.3-2: Message BEARER RESOURCE ALLOCATION REJECT (step 4, Table 10.7.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.7.3.3.3-3: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 5, Table 10.7.3.3.2-1)

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

The same value as the value set in BEARER RESOURCE ALLOCATION REQUEST message in step 3.

Linked EPS bearer identity

5

Table 10.7.3.3.3-4: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT (step 6, Table 10.7.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.7.4 UE requested bearer resource allocation / Expiry of timer T3480

10.7.4.1 Test Purpose (TP)

(1)

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

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

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

}

(2)

with { UE has sent the BEARER RESOURCE ALLOCATION REQUEST message 5 times }

ensure that {
when { UE detects fifth expiry of timer T3480 }

then { UE does not re-send a BEARER RESOURCE ALLOCATION REQUEST message }

}

10.7.4.2 Conformance requirements

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

[TS 24.301, clause 6.5.3.2]

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

…

[TS 24.301, clause 6.5.3.5]

a) Expiry of timer T3480:

On the first expiry of the timer T3480, the UE shall resend the BEARER RESOURCE ALLOCATION REQUEST and shall reset and restart timer T3480. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3480, the UE shall abort the procedure, release the PTI allocated for this activation and enter the state PROCEDURE TRANSACTION INACTIVE.

…

10.7.4.3 Test description

10.7.4.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

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

10.7.4.3.2 Test procedure sequence

Table 10.7.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

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

–

–

–

–

2

The UE transmits a SERVICE REQUEST message.

–>

SERVICE REQUEST

–

–

2A

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

–

–

–

–

3

The UE transmits a BEARER RESOURCE ALLOCATION REQUEST message.

–>

BEARER RESOURCE ALLOCATION REQUEST

–

–

4

Wait for 8 s to ensure that T3480 expires (1st expiry) (see Note 2)

–

–

–

–

5

Check: Does the UE re-transmit a BEARER RESOURCE ALLOCATION REQUEST message?

–>

BEARER RESOURCE ALLOCATION REQUEST

1

P

6

Wait for 8 s to ensure that T3480 expires (2nd expiry) (see Note 2)

–

–

–

–

7

Check: Does the UE re-transmit a BEARER RESOURCE ALLOCATION REQUEST message?

–>

BEARER RESOURCE ALLOCATION REQUEST

1

P

8

Wait for 8 s to ensure that T3480 expires (3rd expiry) (see Note 2)

–

–

–

–

9

Check: Does the UE re-transmit a BEARER RESOURCE ALLOCATION REQUEST message?

–>

BEARER RESOURCE ALLOCATION REQUEST

1

P

10

Wait for 8 s to ensure that T3480 expires (4th expiry) (see Note 2)

–

–

–

–

11

Check: Does the UE re-transmit a BEARER RESOURCE ALLOCATION REQUEST message?

–>

BEARER RESOURCE ALLOCATION REQUEST

1

P

12

Wait for 8 s to ensure that T3480 expires (5th expiry) (see Note 2)

–

–

–

–

13

Check: Does the UE re-transmit a BEARER RESOURCE ALLOCATION REQUEST message?

–>

BEARER RESOURCE ALLOCATION REQUEST

2

F

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

Note 2: If the UE supports CE mode mode B and UE’s usage setting is not voice centric, T3480 takes a value of 16 sec (see TS 24.301 clause 10.3).

10.7.4.3.3 Specific message contents

Table 10.7.4.3.3-1: Message BEARER RESOURCE ALLOCATION REQUEST (step 3,5,7,9,11, Table 10.7.4.3.2-1)

Derivation path: 36.508 table 4.7.3-6B

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

5

10.7.5 UE requested bearer resource allocation / BEARER RESOURCE ALLOCATION REJECT message including cause #43 "invalid EPS bearer identity"

10.7.5.1 Test Purpose (TP)

(1)

with { UE has sent the BEARER RESOURCE ALLOCATION REQUEST message in order to establish dedicated EPS bearer between the additional PDN and the UE }

ensure that {
when { UE receives a BEARER RESOURCE ALLOCATION REJECT message with the procedure transaction identity (PTI) indicated in the BEARER RESOURCE ALLOCATION REQUEST message and a cause “invalid EPS bearer identity” }

then { UE deactivates the EPS bearer context(s) corresponding to the additional PDN locally }

}

10.7.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 6.5.1.1, 6.5.1.3, 6.5.3.4 and 6.5.3.5.

[TS 24.301, clause 6.5.1.1]

The purpose of the UE requested PDN connectivity procedure is for a UE to request the setup of a default EPS bearer to a PDN. The UE requests connectivity to a PDN by sending a PDN CONNECTIVITY REQUEST message to the network. If accepted by the network, this procedure initiates the establishment of a default EPS bearer context. The procedure is used either to establish the first default bearer by including the PDN CONNECTIVITY REQUEST message into the initial attach message, or to establish subsequent default bearers to additional PDNs in order to allow the UE simultaneous access to multiple PDNs by sending the message stand-alone.

[TS 24.301, clause 6.5.1.3]

…

If connectivity with the requested PDN is accepted by the network, the MME shall initiate the default EPS bearer context activation procedure (see subclause 6.4.1).

…

[TS 24.301, clause 6.5.3.4]

If the bearer resource allocation requested cannot be accepted by the network, the MME shall send a BEARER RESOURCE ALLOCATION 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 allocation.

The ESM cause value typically indicates one of the following:

…

#43: invalid EPS bearer identity;

…

Upon receipt of a BEARER RESOURCE ALLOCATION REJECT message, the UE shall stop the timer T3480, release the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE TRANSACTION INACTIVE.

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

[TS 24.301, clause 6.5.3.5]

The following abnormal cases can be identified:

…

b) Unknown EPS bearer context

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

10.7.5.3 Test description

10.7.5.3.1 Pre-test conditions

System Simulator:

– Cell A

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

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

10.7.5.3.2 Test procedure sequence

Table 10.7.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 1)

–

–

–

–

2

The UE transmits a SERVICE REQUEST message.

–>

SERVICE REQUEST

–

–

2A

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

–

–

–

–

3

The UE transmits a PDN CONNECTIVITY REQUEST message.

–>

PDN CONNECTIVITY REQUEST

–

–

4

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

<–

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

–

–

–

EXCEPTION: In parallel to the event described in step 5 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.

–

–

–

–

5

The UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message.

–>

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

–

–

6

Cause the UE to request bearer resource allocation of dedicated EPS bearer associated with additional PDN connectivity. (see Note 2)

–

–

–

–

7

The UE transmits a BEARER RESOURCE ALLOCATION REQUEST message.

–>

BEARER RESOURCE ALLOCATION REQUEST

–

–

8

The SS transmits a BEARER RESOURCE ALLOCATION REJECT message.

<–

BEARER RESOURCE ALLOCATION REJECT

–

–

9

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

<–

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

–

–

10

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

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

10.7.5.3.3 Specific message contents

Table 10.7.5.3.3-1: Message PDN CONNECTIVITY REQUEST (step 3, Table 10.7.5.3.2-1)

Derivation path: 36.508 table 4.7.3-20

Information Element

Value/Remark

Comment

Condition

ESM information transfer flag

Not present

Access point name

Arbitrary name

different from first PDN

Table 10.7.5.3.3-2: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 4, Table 10.7.5.3.2-1)

Derivation path: 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

Table 10.7.5.3.3-3: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 5, Table 10.7.5.3.2-1)

Derivation path: 36.508 table 4.7.3-4

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Table 10.7.5.3.3-4: Message BEARER RESOURCE ALLOCATION REQUEST (step 7, Table 10.7.5.3.2-1)

Derivation path: 36.508 table 4.7.3-6B

Information Element

Value/Remark

Comment

Condition

Linked EPS bearer identity

6

Table 10.7.5.3.3-5: Message BEARER RESOURCE ALLOCATION REJECT (step 8, Table 10.7.5.3.2-1)

Derivation path: 36.508 table 4.7.3-6A

Information Element

Value/Remark

Comment

Condition

ESM cause

‘0010 1011’B

Invalid EPS bearer identity

Table 10.7.5.3.3-6: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 9, Table 10.7.5.3.2-1)

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

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

7

Linked EPS bearer identity

6

Table 10.7.5.3.3-7: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT (step 10, Table 10.7.5.3.2-1)

Derivation path: 36.508 table 4.7.3-2

Information Element

Value/Remark

Comment

Condition

ESM cause

‘0010 1011’B

invalid EPS bearer identity