11.2.7 UE has PDN connection for emergency bearer services / Normal tracking area update / Accepted / Local Emergency Numbers List is not sent by the network / Handling of the lists of forbidden tracking areas

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

11.2.7.1 Test Purpose (TP)

(1)

with { UE having established a PDN connection for emergency bearer services }

ensure that {

when { UE moves to another TA and receives a list of equivalent PLMNs in the TRACKING AREA UPDATE ACCEPT message which includes a PLMN which is on the UE list with forbidden PLMNs }

then { UE stores the received list of equivalent PLMNs not removing from the list the forbidden PLMN }

}

(2)

with { UE having established a PDN connection for emergency bearer services and UE has stored a list of equivalent PLMNs which includes a PLMN which is on the UE list with forbidden PLMNs }

ensure that {

when { PDN connection for emergency bearer services is released }

then { UE removes from the list of equivalent PLMNs any PLMN code present in the list of forbidden PLMNs }

}

(3)

with { UE having received a Local Emergency Numbers List }

ensure that {

when { UE does not receive a new Local Emergency Numbers List when roaming in the area with the same MCC code }

then { UE keeps the old Local Emergency Numbers List }

}

11.2.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clauses 5.5.3.2.2, 5.5.3.2.4 and 5.3.7.

[TS 24.301 clause 5.5.3.2.2]

…

If a UE has uplink user data pending when it initiates the tracking area updating procedure, or uplink signalling not

related to the tracking area updating procedure, it may also set an "active" flag in the TRACKING AREA UPDATE

REQUEST message to indicate the request to establish the user plane to the network and to keep the NAS signalling

connection after the completion of the tracking area updating procedure.

…

[TS 24.301 clause 5.5.3.2.4]

If due to regional subscription restrictions or access restrictions the UE is not allowed to access the TA, but it has a PDN connection for emergency bearer services established, the MME may accept the TRACKING AREA UPDATE REQUEST message and deactivate all non-emergency EPS bearer contexts by initiating an EPS bearer context deactivation procedure when the TAU is initiated in EMM-CONNECTED mode. When the TAU is initiated in EMM-IDLE mode, the MME locally deactivates all non-emergency EPS bearer contexts and informs the UE via the EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message. The MME shall not deactivate the emergency EPS bearer contexts. The network shall consider the UE to be attached for emergency bearer services only and shall indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that ISR is not activated.

…

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. If a default EPS bearer context is marked as inactive in the EPS bearer context status IE included in the TRACKING AREA UPDATE ACCEPT message, and this default bearer is not associated with the last PDN in the UE, the UE 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 MME. If only the PDN connection for emergency bearer services remains established, the UE shall consider itself attached for emergency bearer services only.

The MME may also include of list of equivalent PLMNs in the TRACKING AREA UPDATE ACCEPT message. Each entry in the list contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, and if there is no PDN connection for emergency bearer services established, the UE shall remove from the list any PLMN code that is already in the list of forbidden PLMNs. If there is a PDN connection for emergency bearer services established, the UE shall remove from the list of equivalent PLMNs any PLMN code present in the list of forbidden PLMNs when the PDN connection for emergency bearer services is released. In addition, the UE shall add to the stored list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the TRACKING AREA UPDATE ACCEPT message. If the TRACKING AREA UPDATE ACCEPT message does not contain a list, then the UE shall delete the stored list.

If the UE is not attached for emergency bearer services and if the PLMN identity of the registered PLMN is a member of the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service", any such PLMN identity shall be deleted from the corresponding list(s).

The network may also indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that ISR is active. If the UE is attached for emergency bearer services, the network shall indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that ISR is not activated. If the TRACKING AREA UPDATE ACCEPT message contains:

i) no indication that ISR is activated, the UE shall set the TIN to "GUTI";

ii) an indication that ISR is activated, the UE shall regard a previously assigned P-TMSI and RAI as valid and registered with the network. If the TIN currently indicates "P-TMSI", the UE shall set the TIN to "RAT-related TMSI".

The network informs the UE about the support of specific features, such as IMS voice over PS session, location services (EPC-LCS, CS-LCS) or emergency bearer services, in the EPS network feature support information element. In a UE with IMS voice over PS capability, the IMS voice over PS session indicator and the emergency bearer services indicator shall be provided to the upper layers. The upper layers take the IMS voice over PS session indicator into account as specified in 3GPP TS 23.221 [8A], subclause 7.2a, when selecting the access domain for voice sessions or calls. When initiating an emergency call, the upper layers also take the emergency bearer services indicator into account for the access domain selection. In a UE with LCS capability, location services indicators (EPC-LCS, CS-LCS) shall be provided to the upper layers. When MO-LR procedure is triggered by the UE’s application, those indicators are taken into account as specified in 3GPP TS 24.171 [13C].

[TS 24.301 clause 5.3.7]

The Local Emergency Numbers List contains additional emergency numbers used by the serving network. The list can be downloaded by the network to the UE at successful registration and subsequent registration updates. There is only one Local Emergency Numbers List in the UE, and it can be updated with EMM procedures if the UE is in S1 mode and with GMM and MM procedures if the UE is in A/Gb or Iu mode.

The UE shall use the stored Local Emergency Numbers List received from the network in addition to the emergency numbers stored on the USIM or user equipment to detect that the number dialled is an emergency number.

…

The emergency number(s) received in the Emergency Number List IE are valid only in networks with the same MCC as in the cell on which this IE is received. If no Local Emergency Numbers List is contained in the ATTACH ACCEPT or in the TRACKING AREA UPDATE ACCEPT message, then the stored Local Emergency Numbers List in the user equipment shall be kept, except if the user equipment has successfully registered to a PLMN with an MCC different from that of the last registered PLMN.

11.2.7.3 Test description

11.2.7.3.1 Pre-test conditions

System Simulator:

– Cell A is set to ”Serving cell”;

– Cell B is set to ”Non-Suitable cell”;

– Cell G is set to ”Non-Suitable Off cell”

– Cell I is set to ”Non-Suitable Off cell”

– Cell A and Cell B are on the same PLMN1, Cell G is on different PLMN2 and Cell I is on different PLMN3. PLMN1 and PLMN2 have the same MCC

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

UE:

– USIM contains 2 Emergency Numbers (see TS 22.101 clause 10.1.1).

– PLMN2 is in the USIM’s list with forbidden PLMNs

Preamble:

– the UE is in state Registered, Idle Mode (state 2) on Cell A according to TS 36.508 [18] with a PDN connection for emergency bearer services established (i.e. an Emergency call established according to TS 36.508 [18] section 4.5A.4 and released using the generic procedure in TS 34.229-1 [35] subclause C.32).

Table 11.2.7.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

–

The SS configures:

Cell B as the "Serving cell".

Cell A as a "Non-Suitable Off cell".

–

–

–

–

–

The following messages are to be observed on Cell B unless explicitly stated otherwise.

–

–

–

–

1

The UE transmits a TRACKING AREA UPDATE REQUEST message.

–>

TRACKING AREA UPDATE REQUEST

–

–

2

The SS transmits a TRACKING AREA UPDATE ACCEPT message providing a list of equivalent PLMNs which includes PLMN2 and PLMN3 of which PLMN2 is on the UE list with forbidden PLMNs and providing a Local Emergency Numbers List.

<–

TRACKING AREA UPDATE ACCEPT

–

–

3

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

–>

TRACKING AREA UPDATE COMPLETE

–

–

3A

The SS transmits an RRCConnectionRelease message.

–

RRCConnectionRelease

–

–

–

The SS configures:

Cell G as the "Serving cell".

Cell B as a " Non-Suitable Off cell"

–

–

–

–

–

The following messages are to be observed on Cell G unless explicitly stated otherwise.

–

–

–

–

4

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

–>

TRACKING AREA UPDATE REQUEST

1

P

5

The SS transmits a TRACKING AREA UPDATE ACCEPT message providing a list of equivalent PLMNs which includes PLMN1 (the UE is expected to store the provided PLMN and add to the stored list the PLMN code of the registered PLMN that sent the list (PLMN2). No Local Emergency Numbers List is provided (Note 4).

<–

TRACKING AREA UPDATE ACCEPT

–

–

6

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

–>

TRACKING AREA UPDATE COMPLETE

–

–

6A

Void

–

–

–

–

–

EXCEPTION: Steps 6Ba1-6Ba2 describe optional behaviour that depends on the UE implementation.

–

–

–

–

6Ba1

The UE transmits a DETACH REQUEST message with the Detach type IE value matching the previous Attach type IE value to regain normal service within 5 seconds (Note 5).

–>

DETACH REQUEST

–

–

6Ba2

The SS responds with a DETACH ACCEPT message.

<–

DETACH ACCEPT

–

–

6Ca1

If steps 6Ba1 and 6Ba2 do not take place within 5 secs from step 6, the SS transmits a DETACH REQUEST message with the Detach type IE indicating “re-attach required” to regain normal service (Note 6).

<–

DETACH REQUEST

–

–

6Ca2

The UE responds the DETACH ACCEPT message.

–>

DETACH ACCEPT

–

–

10A

The SS transmits an RRCConnectionRelease message (Note 7).

–

RRCConnectionRelease

–

–

10B

Void

–

–

–

–

10C

Void

–

–

–

–

–

The SS configures:

Cell A as the "Serving cell".

Cell G as a "Non-Suitable Off cell".

–

–

–

–

10D

Void

–

–

–

–

–

The following messages are to be observed on Cell A unless explicitly stated otherwise.

–

–

–

–

11a1

Void

–

–

–

–

11b1

Void

–

–

–

–

11A

Generic procedure for UE registration on Cell A as described in 36.508 Table 4.5.2.3-1 takes place. No Local Emergency Numbers List is provided.

–

–

–

–

12

Cause the UE to start a "call" using one of the Emergency Numbers received at step 2 in the TRACKING AREA UPDATE ACCEPT message within IE Local Emergency Numbers List (Note 2).

–

–

–

–

13

Check: Does UE transmit an RRCConnectionRequest message with establishmentCause set to ‘emergency"?

–>

RRCConnectionRequest

3

P

14-14L

Steps 3-15 from the Generic Test Procedure for IMS Emergency call establishment in EUTRA: Normal Service as described in 36.508 Table 4.5A.4.3-1 take place, with the IMS emergency registration being optional.

–

–

–

–

15

The SS waits 1 second.

–

–

–

–

15A

Void.

–

–

–

–

16

Void.

–

–

–

–

16A

Void.

–

–

–

–

16B

Void.

–

–

–

–

16C

IMS Call is released (Note 10).

–

–

–

–

17

The SS releases the RRC connection.

–

–

–

–

–

The SS configures:
Cell B as the "Serving cell".

Cell A as a "Non-Suitable Off cell".

–

–

–

–

–

The following messages are to be observed on Cell B unless explicitly stated otherwise.

–

–

–

–

18

The UE transmits a TRACKING AREA UPDATE REQUEST message.

–>

TRACKING AREA UPDATE REQUEST

–

–

18A

The SS transmits a SecurityModeCommand message to activate AS security.

<–

RRC: SecurityModeCommand

–

–

18B

The UE transmits a SecurityModeComplete message and establishes the initial security configuration.

–>

RRC: SecurityModeComplete

–

–

18C

The SS transmits a RRCConnectionReconfiguration message to establish SRB2 and the data radio bearers associated with the default EPS bearer context for IMS PDN, and the default EPS bearer context for the Emergency PDN (Note 11).

<–

RRC: RRCConnectionReconfiguration

–

–

18D

The UE transmits a RRCConnectionReconfigurationComplete message.

–>

RRC: RRCConnectionReconfigurationComplete

–

–

19

The SS transmits a TRACKING AREA UPDATE ACCEPT message providing a list of equivalent PLMNs which includes PLMN2 and PLMN3 with PLMN2 on the UE list with forbidden PLMNs.

<–

TRACKING AREA UPDATE ACCEPT

–

–

20

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

–>

TRACKING AREA UPDATE COMPLETE

–

–

21

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

–

–

22

The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT.

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

–

23

The SS transmits an RRCConnectionRelease message (Note 8).

–

RRCConnectionRelease

–

–

–

The SS configures:

Cell B as a "Non-Suitable Off cell".

Cell I as a "Suitable cell".

Cell G as the "Serving Cell".

–

–

–

–

–

The following messages are to be observed on Cell I unless explicitly stated otherwise.

–

–

–

–

24

Check: Does the UE transmit a TRACKING AREA UPDATE REQUEST message (Note 9) ?

–>

TRACKING AREA UPDATE REQUEST

2

P

25

The SS transmits a TRACKING AREA UPDATE ACCEPT message.

<–

TRACKING AREA UPDATE ACCEPT

–

–

26

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

–>

TRACKING AREA UPDATE COMPLETE

–

–

27

The SS releases the RRC connection.

–

–

–

–

–

EXCEPTION: Step 27a1

describes optional behaviour that depends on

the UE capability.

–

–

–

–

27a1

The UE may attempt the generic test procedure for IMS Re-registration on EPS VPLMN as specified in TS 36.508 [18] subclause 4.5A.30.

–

–

–

–

–

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

–

–

–

–

Note 1: Void.

Note 2: The request to originate an emergency service may be performed by MMI or AT command.

Note 3: Void.

Note 4: When the TAU is initiated in EMM-IDLE mode, the MME locally deactivates all non-emergency EPS bearer contexts and informs the UE via the EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message. The MME shall not deactivate the emergency EPS bearer contexts. The network shall consider the UE to be attached for emergency bearer services only and shall indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that ISR is not activated.

Note 5: Having released all other bearers and being attached only for emergency services, the UE may DETACH and thus disconnect from the emergency PDN in order to gain normal service; i.e. UE released the Emergency Bearer.

Note 6: A collision of UE initiated DETACH (steps 6Ba1 – 6Ba2) and network initiated DETACH may occur despite of waiting for 5 secs. Such collision shall not result in a FAIL / INCONCLUSIVE verdict.

Note 7: The forbidden PLMN list is unchanged. PLMNs on the Equivalent PLMN list which are in the FPLMN list are removed from the EPLMN list. So Cell G is removed from the EPLMN list. The EPLMN list is deleted when the UE attached for emergency bearer services enters the state EMM-DEREGISTERED.

Note 8: The forbidden PLMN list is unchanged. PLMNs on the Equivalent PLMN list which are in the FPLMN list are removed from the EPLMN list. So Cell G is removed from the EPLMN list, cell I is still on the EPLMN list. The UE is no longer emergency attached.

Note 9: The UE accesses Cell I because its PLMN is in the EPLMN list.

Note 10: The IMS Call is released using the generic procedure in TS 34.229-1 [35] subclause C.32.

Note 11: After TAU procedure has been completed, there are no user plane radio bearers active on Cell B. User plane radio bearers need to be re-established as the DRB for Emergency PDN is released in subsequent step21.

11.2.7.3.3 Specific message contents

Table 11.2.7.3.3-1: Message ATTACH ACCEPT (in the preamble)

Derivation path: 36.508 table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

EPS network feature support

‘0000 0111’B

– IMS voice over PS session in S1 mode supported

– emergency bearer services in S1 mode supported

– location services via EPC supported

– no information about support of location services via CS domain is available

Table 11.2.7.3.3-1A: TRACKING AREA UPDATE REQUEST (steps 1, 4 and 18, Table 11.2.7.3.2-1)

Derivation Path: 36.508 clause 4.7.2-27

Information Element

Value/remark

Comment

Condition

EPS update type

"Active" flag

‘?’B

Table 11.2.7.3.3-2: Message TRACKING AREA UPDATE ACCEPT (step 2, Table 11.2.7.3.2-1)

Derivation path: 36.508 table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

–

Includes MCC and MNC digits for PLMN2 and PLMN3

Emergency number list

2 numbers

TS 24.008, 10.5.3.13

The numbers shall be different than any of those indicated in TS 22.101 clause 10.1.1 AND the numbers stored in the USIM AND any emergency number stored permanently in the ME

EPS network feature support

‘0000 0111’B

– IMS voice over PS session in S1 mode supported

– emergency bearer services in S1 mode supported

– location services via EPC supported

– no information about support of location services via CS domain is available

Table 11.2.7.3.3-3: Message TRACKING AREA UPDATE ACCEPT (step 5, Table 11.2.7.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 default EPS bearer

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)

’010’B

Non-Emergency EPS bearer context is inactive

EBI(8)-EBI(15)

0

Emergency number list

–

This IE is not present.

Equivalent PLMNs

–

Includes MCC and MNC digits for PLMN1 and PLMN3

EPS network feature support

‘0000 0111’B

– IMS voice over PS session in S1 mode supported

– emergency bearer services in S1 mode supported

– location services via EPC supported

– no information about support of location services via CS domain is available

Table 11.2.7.3.3-4: Void

Table 11.2.7.3.3-5: Message RRCConnectionRequest (step 13, Table 11.2.7.3.2-1)

Derivation path: 36.508 table 4.6.1-16

Information Element

Value/Remark

Comment

Condition

RRCConnectionRequest ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r8 SEQUENCE {

establishmentCause

emergency

}

}

}

Table 11.2.7.3.3-5A: Message RRCConnectionReconfiguration (step 18C, Table 11.2.7.3.2-1)

Derivation Path: 36.508 clause 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

dedicatedInfoNASList

Not present

radioResourceConfigDedicated

RadioResourceConfigDedicated-SRB2-DRB(2, 0)

}

}

}

}

Table 11.2.7.3.3-5AA: Message TRACKING AREA UPDATE ACCEPT (step 19, Table 11.2.7.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 default EPS bearer

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)

’110’B

EBI(8)-EBI(15)

0

Equivalent PLMNs

–

Includes MCC and MNC digits for PLMN2 and PLMN3

EPS network feature support

‘0000 0111’B

– IMS voice over PS session in S1 mode supported

– emergency bearer services in S1 mode supported

– location services via EPC supported

– no information about support of location services via CS domain is available

Table 11.2.7.3.3-6: Void

Table 11.2.7.3.3-7: Void

Table 11.2.7.3.3-8: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 21, Table 11.2.7.3.2-1)

Derivation path: 36.508 table 4.7.3-12 and table 4.6.1-8 with condition and condition NETWORK-INITIATED

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

Default EBId-2

ESM cause

‘0010 0100’B

regular deactivation