10.4 EPS bearer context deactivation

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.4.1 EPS bearer context deactivation / Success

10.4.1.1 Test Purpose (TP)

(1)

with { UE is in BEARER CONTEXT ACTIVE STATE and in EMM-CONNECTED mode }

ensure that {

when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message }

then { UE deletes the EPS bearer context identified by the EPS bearer identity and transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT }

}

(2)

with { UE is in BEARER CONTEXT ACTIVE STATE and in EMM-CONNECTED mode }

ensure that {

when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message indicating the EPS bearer identity of the default bearer to a PDN }

then { UE deletes all EPS bearer contexts identified to the PDN and transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT }

}

(3)

with { UE is in BEARER CONTEXT ACTIVE STATE and in EMM-CONNECTED mode }

ensure that {

when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message that does not point to an existing EPS bearer context }

then { UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT with EPS bearer identity set to the received EPS bearer identity }

}

(4)

with { UE is in BEARER CONTEXT ACTIVE STATE and in EMM-IDLE mode }

ensure that {

when { UE initiates an EMM-IDLE to EMM-CONNECTED transition (i.e. SERVICE REQUEST, TRACKING AREA UPDATE REQUEST) }

then { UE only synchronizes EPS bearer context state(s) which are explicitly activated by SS in signalling messages }

}

10.4.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.4.4.2, 5.5.3.2.4, 5.6.1.4, 6.4.4.3 and 6.4.4.6.

[TS 24.301, clause 6.4.4.2]

When the MME wants to deactivate all EPS bearer contexts to a PDN and thus disconnect the UE from the PDN, the MME shall include the EPS bearer identity of the default bearer associated to the PDN in the DEACTIVATE EPS BEARER CONTEXT REQUEST message.

If no NAS signalling connection exists when the MME initiates the EPS bearer context deactivation, the ESM entity in the MME shall locally deactivate the EPS bearer context towards the UE without any peer-to-peer ESM signalling between the MME and the UE.

NOTE: The EPS bearer context state(s) can be synchronized between the UE and the MME at the next EMM-IDLE to EMM-CONNECTED transition, e.g. during a service request or tracking area updating procedure.

[TS 24.301, clause 5.6.1.4]

The UE shall locally deactivate the EPS bearer contexts that do not have a user plane radio bearer established after the successful completion of the service request procedure.

[TS 24.301, clause 5.5.3.2.4]

If an EPS bearer context status IE is included in the TRACKING AREA UPDATE REQUEST message, the MME shall deactivate all those EPS bearer contexts locally (without peer-to-peer signalling between the MME and the UE) which are active on the network side, but are indicated by the UE as being inactive. If a default EPS bearer context is marked as inactive in the EPS bearer context status IE included in the TRACKING AREA UPDATE REQUEST message, and this default bearer is not associated with the last PDN of the user in the MME, the MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE.

If the EPS bearer context status IE is included in the TRACKING AREA UPDATE REQUEST, the MME shall include an EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message, indicating which EPS bearer contexts are active in the MME.

If an EPS bearer context status IE is included in the TRACKING AREA UPDATE ACCEPT message, the UE shall deactivate all those EPS bearers contexts locally (without peer-to-peer signalling between the UE and the MME) which are active in the UE, but are indicated by the MME as being inactive.

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

If the EPS bearer identity indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST is that of the default bearer to a PDN, the UE shall delete all EPS bearer contexts associated to the PDN. After deactivating all EPS bearer contexts, 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 PTI is included in the DEACTIVATE EPS BEARER CONTEXT REQUEST message, 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 PTI is included in the DEACTIVATE EPS BEARER CONTEXT REQUEST message, 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 DEACTIVATE 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 DEACTIVATE EPS BEARER CONTEXT ACCEPT message with the EPS bearer identity set to the received EPS bearer identity.

[TS 24.301, clause 6.4.4.6]

The UE and the MME deactivate EPS bearer contexts locally without peer-to-peer ESM signalling in the following cases:

1) during the service request procedure, if the E-UTRAN fails to establish the user plane radio bearers for one or more EPS bearer contexts e.g. due to radio access control;

…For those cases, based on the indication from the lower layers, the UE and the MME shall locally deactivate the EPS bearer contexts for which no user plane radio bearers are set up.

When the user plane radio bearer for a default EPS bearer context is not established during the service request procedure or tracking area updating procedure with "active" flag, the UE shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context. The MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE.

10.4.1.3 Test description

10.4.1.3.1 Pre-test conditions

System Simulator:

– Cell A and Cell B are configured according to Table 6.3.2.2-1 in [18].

– Cell A, Cell B (home PLMN, different TAs).

– System information combination 3 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells;

UE:

None.

Preamble:

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

10.4.1.3.2 Test procedure sequence

Table 10.4.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

Cell A is the serving cell

Cell B is a suitable cell

1

Cause the UE to request connectivity to an additional PDN (see Note 1)

1A

The UE transmits a SERVICE REQUEST

–>

SERVICE REQUEST

1B

The SS establishes SRB2 and DRB associated with default EPS bearer context obtained during the attach procedure.

2

The UE transmits a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN.

–>

PDN CONNECTIVITY REQUEST

3

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

Note: the SS allocates a PDN address of a PDN type which is compliant with the PDN type requested by the UE.

<–

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

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

4

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

–>

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

5

The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST relative to the additional PDN.

Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 3.

<–

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

6

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified.

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

7

The SS releases the RRC connection.

8

The SS transmits a Paging message to the UE using S-TMSI with CN domain indicator set to ”PS”.

<–

9

The UE transmits the SERVICE REQUEST message

–>

SERVICE REQUEST

9A

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

10

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST including the EPS bearer identity of the dedicated EPS bearer to the additional PDN.

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

11

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

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

1

P

12

The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST relative to the additional PDN.

Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 3.

<–

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

13

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified.

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

14

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST including the EPS bearer identity of the default EPS bearer to the additional PDN.

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

15

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

(see Note 3)

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

2

P

16

The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message including the EPS bearer identity of the dedicated EPS bearer. This message is included in a DLInformationTransfer message.

<–

MODIFY EPS BEARER CONTEXT REQUEST

17

Check: Does UE transmit a MODIFY EPS BEARER CONTEXT REJECT message with ESM cause #43? (see Note 4)

–>

MODIFY EPS BEARER CONTEXT REJECT

2

P

18

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST that does not point an existing EPS bearer context.

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

19

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

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

3

P

20

The SS releases the RRC connection.

21

Cause the UE to request connectivity to an additional PDN (see note 1)

21A

The UE transmits a SERVICE REQUEST

–>

SERVICE REQUEST

21B

The SS establishes SRB2 and DRB associated with default EPS bearer context obtained during the attach procedure

22

The UE transmits a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN.

–>

PDN CONNECTIVITY REQUEST

23

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

<–

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

24

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

–>

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

25

The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST relative to additional PDN.

Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 3.

<–

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

26

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified.

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

27

The SS releases the RRC connection.

28

The SS transmits a Paging message to the UE using S-TMSI with CN domain indicator set to ”PS”.

<–

29

The UE transmits SERVICE REQUEST message

–>

SERVICE REQUEST

30

The SS performs a radio bearer establishment procedure. (Note 2)

The RRCConnectionReconfiguration message doesn’t include the EPS bearer ID of the additional PDN.

31

Check: Does UE transmit an RRCConnectionReconfigurationComplete message? (Note 2)

4

P

32

The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message including the EPS bearer identity of the default EPS bearer to the additional PDN. This message is included in a DLInformationTransfer message.

<–

MODIFY EPS BEARER CONTEXT REQUEST

32A

Check: Does UE transmits a MODIFY EPS BEARER CONTEXT REJECT message with ESM cause #43?(see Note 3)

–>

MODIFY EPS BEARER CONTEXT REJECT

4

P

32B

The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message including the EPS bearer identity of the dedicated EPS bearer.

<–

MODIFY EPS BEARER CONTEXT REQUEST

32C

Check: Does UE transmit a MODIFY EPS BEARER CONTEXT REJECT message with ESM cause #43? (see Note 4)

–>

MODIFY EPS BEARER CONTEXT REJECT

4

P

33

The SS releases the RRC connection.

34

Cause the UE to request connectivity to an additional PDN (see note 1)

34A

The UE transmits a SERVICE REQUEST

–>

SERVICE REQUEST

34B

The SS establishes SRB2 and DRB associated with default EPS bearer context obtained during the attach procedure

35

The UE transmits a PDN CONNECTIVITY REQUEST message as specified to request an additional PDN.

–>

PDN CONNECTIVITY REQUEST

36

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

Note: SS allocates a PDN address of a PDN type which is compliant with the PDN type requested by the UE.

<–

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

37

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

–>

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

38

The SS transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST relative to additional PDN.

Note: the same PDN address is applicable because the linked EPS bearer ID refers to the default EBC allocated in step 3.

<–

ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST

39

The UE transmits an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message as specified.

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

40

The SS releases the RRC connection.

41

Cell A is a suitable cell

Cell B is the serving cell

42

The UE transmits a TRACKING AREA UPDATE REQUEST message as specified on Cell B.

–>

TRACKING AREA UPDATE REQUEST

42A

The SS establishes SRB2 and DRB associated with default EPS bearer context obtained during the attach procedure.

43

The SS transmits a TRACKING AREA UPDATE ACCEPT indicating only one EPS bearer (default EBId-1) active in the EPS bearer context status IE.

Note:

The EPS bearer ID linked to the additional PDN is deactivated by SS.

<–

TRACKING AREA UPDATE ACCEPT

43AA

The UE transmits TRACKING AREA UPDATE COMPLETE message

–>

TRACKING AREA UPDATE COMPLETE

43AB

Void

43A

The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message including the EPS bearer identity of the default EPS bearer to the additional PDN. This message is included in a DLInformationTransfer message.

<–

MODIFY EPS BEARER CONTEXT REQUEST

43B

Check: Does UE transmits a MODIFY EPS BEARER CONTEXT REJECT message with ESM cause #43?(see Note 3)

–>

MODIFY EPS BEARER CONTEXT REJECT

4

P

43C

The SS transmits a MODIFY EPS BEARER CONTEXT REQUEST message including the EPS bearer identity of the dedicated EPS bearer. This message is included in a DLInformationTransfer message.

<–

MODIFY EPS BEARER CONTEXT REQUEST

43D

Check: Does UE transmit a MODIFY EPS BEARER CONTEXT REJECT message with ESM cause #43? (see Note 4)

–>

MODIFY EPS BEARER CONTEXT REJECT

4

P

44

The SS releases the RRC connection.

EXCEPTION: Step 45 & 46 describe behaviour that depends on the UE capability.

45

If pc_ESM_MO_Bearer_Allocation cause the UE to request bearer resource allocation of dedicated EPS bearer associated with additional PDN connectivity.

46

Check: Does the UE transmit SERVICE REQUEST?

–>

SERVICE REQUEST

4

F

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

Note 2: After a correct SERVICE REQUEST is received then the SS performs the Radio Bearer Establishment procedure. The UE transmission of the RRCConnectionReconfigurationComplete message indicates the completion of the radio bearer establishment procedure and that the UE has changed EMM mode from EMM-IDLE to EMM-CONNECTED.

Note 3: It can be confirmed that the additional default EPS bearer has been deactivated by UE.

Note 4: It can be confirmed that the dedicated EPS bearer has been deactivated by UE.

10.4.1.3.3 Specific message contents

Table 10.4.1.3.3-1: Message PDN CONNECTIVITY REQUEST (step 2, 22 and 35, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-20

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

0000

No EPS bearer identity assigned

Procedure transaction identity

PTI-1

UE assigns a particular PTI not yet used between 1 and 254

ESM information transfer flag

Not present

This IE is only used during an attach procedure.

Access point name

APN-1 (New PDN name)

The requested PDN is different from default PDN

Table 10.4.1.3.3-2: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 3, 23 and 36, Table 10.4.1.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

SS assigns an additional EPS Bearer Id different from default EPS Bearer Id between 5 and 15.

Procedure transaction identity

PTI-1

SS re-uses the particular PTI defined by UE for this present additional PDN connectivity request procedure.

Access point name

APN-1

SS re-uses the particular APN defined by UE for this present additional PDN connectivity request procedure

Table 10.4.1.3.3-3: Message ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT (step 4, 24 and 37, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-4

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Same value as in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

Procedure transaction identity

0

No procedure transaction identity assigned

Table 10.4.1.3.3-4: Message ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST (step 5, 12, 25 and 38, Table 10.4.1.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

SS assigns a dedicated bearer Id different from default EBId and additional EBId and between 5 and 15.

Procedure transaction identity

0

No procedure transaction identity assigned

Linked EPS bearer identity

Default EBId-2 (same value like in table 10.4.1.3.3-2)

EPS QoS

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

SS defines an additional dedicated EPS QoS

TFT

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

Table 10.4.1.3.3-5: Message ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT (step 6, 13, 26 and 39, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-1

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

7

Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST in step 5

Procedure transaction identity

0

No procedure transaction identity assigned

Table 10.4.1.3.3-6: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 10, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-12 and table 4.6.1-8 with condition DRB-REL(3)

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

7

Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST of step 5

Procedure transaction identity

0

No procedure transaction identity assigned

ESM cause

00100100

regular deactivation

Protocol configuration options

Not present

Table 10.4.1.3.3-7: Message DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 11, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-11

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

7

Same value as in ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST of step 5

Procedure transaction identity

0

No procedure transaction identity assigned

Table 10.4.1.3.3-8: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 14, Table 10.4.1.3.2-1)

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

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

Default EBId-2

Same value as in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST of step 3

Procedure transaction identity

0

No procedure transaction identity assigned

ESM cause

00100100

regular deactivation

Protocol configuration options

Not present

Table 10.4.1.3.3-9: Message DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 15, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-11

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Same value as in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST of step 3

Procedure transaction identity

0

No procedure transaction identity assigned

Table 10.4.1.3.3-9b: Message MODIFY EPS BEARER CONTEXT REQUEST (step 16, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-16

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

7

Dedicated EPS bearer context which should have been deactivated

Procedure transaction identity

0

"No procedure transaction identity assigned"

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

Replace packet filters in existing TFT

Table 10.4.1.3.3-10: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 18, Table 10.4.1.3.2-1)

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

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

This value does not refer to an existing EPS bearer

Procedure transaction identity

0

No procedure transaction identity assigned

ESM cause

00100100

regular deactivation

Protocol configuration options

Not present

Table 10.4.1.3.3-11: Message DEACTIVATE EPS BEARER CONTEXT ACCEPT (step 19, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-11

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Same value as in DEACTIVATE EPS BEARER CONTEXT REQUEST of step 16

Procedure transaction identity

0

No procedure transaction identity assigned

Table 10.4.1.3.3-11a: Message RRCConnectionReconfiguration (step 30, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.6.1-8 with condition SRB2-DRB(0, 1)

Table 10.4.1.3.3-12: Message MODIFY EPS BEARER CONTEXT REQUEST (step 32 and 43A, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-16

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

SS assigns the additional default EPS bearer context which isn’t present.

Procedure transaction identity

0

No procedure transaction identity assigned

Table 10.4.1.3.3-13: Message MODIFY EPS BEARER CONTEXT REJECT (step 32A and 43B, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-14

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

6

Same value as in MODIFY EPS BEARER CONTEXT REQUEST

Procedure transaction identity

0

No procedure transaction identity assigned

ESM cause

00101011

invalid EPS bearer identity

Table 10.4.1.3.3-14: Message MODIFY EPS BEARER CONTEXT REQUEST (step 16, 32B and 43C, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-16

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

7

SS assigns the dedicated EPS bearer context which isn’t present.

Procedure transaction identity

0

No procedure transaction identity assigned

Table 10.4.1.3.3-15: Message MODIFY EPS BEARER CONTEXT REJECT (step 17, 32C and 43D, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.3-14

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

7

Same value as in MODIFY EPS BEARER CONTEXT REQUEST

Procedure transaction identity

0

No procedure transaction identity assigned

ESM cause

00101011

invalid EPS bearer identity

Table 10.4.1.3.3-16: Message TRACKING AREA UPDATE REQUEST (step 42, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.2-27

Information Element

Value/Remark

Comment

Condition

EPS bearer context status

optional

This IE may be present

EPS bearer context status IEI

57

Length of EPS bearer context status contents

2

2 octets

EBI(0)-EBI(4)

0

EBI(5)-EBI(7)

7

EPS bearer contexts activated in preamble, step 36 and step 38.

EBI(8)-EBI(15)

0

Table 10.4.1.3.3-17: Message TRACKING AREA UPDATE ACCEPT (step 43, Table 10.4.1.3.2-1)

Derivation path: 36.508 table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

EPS bearer context status

present

The SS deactivates the EPS bearer Id of the additional PDN given at step 30.

EPS bearer context status IEI

57

Length of EPS bearer context status contents

2

2 octets

EBI(0)-EBI(4)

0

EBI(5-7)

1

EPS bearer contexts activated in preamble

EBI(8)-EBI(15)

0

10.4.2 EPS bearer context deactivation / Re-establishment

10.4.2.1 Test Purpose (TP)

(1)

with { the UE in BEARER CONTEXT ACTIVE STATE state and EMM-CONNECTED mode }

ensure that {

when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message }

then { the UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT }

}

(2)

with { the UE in BEARER CONTEXT ACTIVE STATE state and EMM-CONNECTED mode and the UE needs to continue having a public user identity registered }

ensure that {

when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message indicating the EPS bearer used for SIP signalling }

then { the UE transmits a PDN CONNECTIVITY REQUEST }

}

(3)

with { the UE in BEARER CONTEXT ACTIVE STATE state and EMM-CONNECTED mode }

ensure that {

when { UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message indicating the EPS bearer used for SIP signalling }

then { the UE performs a new initial IMS registration }

}

10.4.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clauses 6.4.4.2, 6.4.4.3 and 6.4.4.6 and TS 24.229, clause L2.2.1B. Unless otherwise stated these are Rel-8 requirements.

[TS 24.301, clause 6.4.4.2]

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

#8: operator determined barring;

#36: regular deactivation;

#38: network failure; or

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

The procedure transaction identity (PTI) shall also be included if the deactivation is triggered by a UE initiated bearer resource modification procedure or UE requested PDN disconnect procedure.

When the MME wants to deactivate all EPS bearer contexts to a PDN and thus disconnect the UE from the PDN, the MME shall include the EPS bearer identity of the default bearer associated to the PDN in the DEACTIVATE EPS BEARER CONTEXT REQUEST message.

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

If the EPS bearer identity indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST is that of the default bearer to a PDN, the UE shall delete all EPS bearer contexts associated to the PDN. After deactivating all EPS bearer contexts, the UE shall respond to the MME with the DEACTIVATE EPS BEARER CONTEXT ACCEPT.

[TS 24.229, clause L.2.2.1B ”Re-establishment of the EPS bearer context for SIP signalling”]

If the UE registered a public user identity with an IP address allocated for the APN of the EPS bearer context used for SIP signalling, the EPS bearer context used for SIP signalling is deactivated as result of signalling from the network and:

i) if the UE is required to perform an initial registration according to subclause L.3.1.2;

ii) if the signalling from the network results in requiring the UE to initiate activation of the PDN connection of the EPS bearer context used for SIP signalling; or

iii) if the UE needs to continue having a public user identity registered with an IP address allocated for the APN;

the UE shall:

A) if the non-access stratum is performing the UE requested PDN connectivity procedure and the EPS bearer context activation procedure(s) for the APN triggered as result of the signalling from the network, wait until the UE requested PDN connectivity procedure and the EPS bearer context activation procedure(s) for the APN finish; and

B) perform the procedures in subclause L.2.2.1, bullets a), b) and c).

If none of the bullets i), ii) and iii) of this subclause evaluate to true, or the procedures in bullet B) of this subclause were unable to ensure that the EPS bearer context used for SIP signalling is available or were unable to acquire any P-CSCF address(es):

1) if the SIP signalling was carried over a dedicated EPS bearer context, the UE shall release all resources established as a result of SIP signalling by sending to the network either:

a) a BEARER RESOURCE MODIFICATION REQUEST message, if there are EPS bearer contexts to this PDN that are not related SIP sessions; or

b) a PDN DISCONNECT REQUEST message if all the EPS bearer contexts to this PDN are related to SIP sessions.

NOTE: If the SIP signalling was carried over the default EPS bearer context, all the resources established as a result of SIP signalling are released without any explicit NAS signalling.

If the default EPS bearer context of the PDN connection of the EPS bearer context used for SIP signalling was deactivated at the start of this subclause, and the procedures in bullet B) of this subclause ensured that the EPS bearer context used for SIP signalling is available and acquired the P-CSCF address(es), the UE shall perform a new initial registration according to subclause 5.1.1.2.

10.4.2.3 Test description

10.4.2.3.1 Pre-test conditions

System Simulator:

– cell A

UE:

None.

Preamble:

– The UE is in state Switched OFF (state 1) according to [18].

10.4.2.3.2 Test procedure sequence

Table 10.4.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

The UE is switched on.

0A-0Q

Steps 1 to 16c1 of the generic test procedure for UE registration (TS 36.508 4.5.2.3-1).

1

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST including the EPS bearer identity of the default EPS bearer.

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

2

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

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

1

P

3

Check: Does the UE transmit a PDN CONNECTIVITY REQUEST?

–>

PDN CONNECTIVITY REQUEST

2

P

4-12

Void

13

The SS transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST.

<–

ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST

EXCEPTION: In parallel to the event described in step 14 below, if initiated by the UE 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 to the event described in step 14 below the generic procedure for IMS signalling in the U-plane specified in table 10.4.2.3.2-2 takes place.

14

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

–>

ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT

15

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST including the EPS bearer identity of the internet PDN.

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

16

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

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

Table 10.4.2.3.2-2: Procedure for IMS signalling in the U-plane

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-9

Registration procedure according TS 34.229-1 [43] subclause C.2 (steps 3-11).

3

P

10.4.2.3.3 Specific message contents

Table 10.4.2.3.3-1: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 1, Table 10.4.2.3.2-1)

Derivation path: 36.508 table 4.7.3-12 and table 4.6.1-8 with condition DRB-REL(1)

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

EPS bearer identity

Same value as in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST for the IMS APN from preamble

Procedure transaction identity

0

No procedure transaction identity assigned

ESM cause

00100100

regular deactivation

Protocol configuration options

Not present