11.2.6 Handling of Local Emergency Numbers List provided during Attach and Normal tracking area update procedures

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.6.1 Test Purpose (TP)

(1)

with { UE in state EMM-REGISTERED and EMM-IDLE mode, Emergency numbers stored in the USIM and a Local Emergency Numbers List provided during the Attach procedure }

ensure that {

when { UE is requested to initiate a call with a number belonging to the emergency numbers stored in the USIM }

then { UE initiates an emergency call }

}

(2)

with { UE in state EMM-REGISTERED and EMM-IDLE mode, Emergency numbers stored in the USIM and a Local Emergency Numbers List provided during the Attach procedure }

ensure that {

when { UE performs a tracking area update to a new tracking area not included in the TAI list and belonging to a network with the same MCC and the TRACKING AREA UPDATE ACCEPT message sent by the network includes a Local Emergency Numbers List with 10 new numbers }

then { UE overwrites the old list with the new one and recognises each of the new numbers as an emergency number }

}

(3)

with { UE in state EMM-REGISTERED and EMM-IDLE mode, Emergency numbers stored in the USIM and a Local Emergency Numbers List provided during a tracking area update }

ensure that {

when { UE performs a tracking area update to a new tracking area not included in the TAI list and not belonging to a network with the same MCC }

then { UE recognises the numbers stored in the USIM as emergency numbers }

}

(4)

with { UE in state EMM-REGISTERED and EMM-IDLE mode, Emergency numbers stored in the USIM and a Local Emergency Numbers List provided during the Attach procedure }

ensure that {

when { UE is requested to initiate a call with a number belonging to the Local Emergency Numbers List }

then { UE initiates an emergency call }

}

11.2.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 24.301 clause 5.3.7, TS 22.101 clause 10.1.1.

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

NOTE: The user equipment may use the emergency numbers list to assist the end user in determining whether the dialled number is intended for an emergency service or for another destination, e.g. a local directory service. The possible interactions with the end user are implementation specific.

The network may send a Local Emergency Numbers List in the ATTACH ACCEPT or in the TRACKING AREA UPDATE ACCEPT messages, by including the Emergency Number List IE. The user equipment shall store the Local Emergency Numbers List, as provided by the network, except that any emergency number that is already stored in the USIM shall be removed from the Local Emergency Numbers List before it is stored by the user equipment. If there are no emergency numbers stored on the USIM, then before storing the received Local Emergency Numbers List, the user equipment shall remove from the Local Emergency Numbers List any emergency number stored permanently in the user equipment for use in this case (see 3GPP TS 22.101 [8]). The Local Emergency Numbers List stored in the user equipment shall be replaced on each receipt of a new Emergency Number List IE.

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.

The Local Emergency Numbers List shall be deleted at switch off and removal of the USIM. The user equipment shall be able to store up to ten local emergency numbers received from the network.

[TS 24.301 clause 5.6.1.5A]

If the service request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the UE shall perform the procedures as described in subclause 5.6.1.5. Then if the UE is in the same selected PLMN where the last service request was attempted, the UE shall:

a) inform the upper layers. This could result in the UE attempting a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229 [13D] that can result in the emergency call being attempted to another IP-CAN; or

b) detach locally, if not detached already, attempt EPS attach for emergency bearer services.

If the service request for initiating a PDN connection for emergency bearer services fails due to abnormal cases b), c) or e) in subclause 5.6.1.6, the UE shall perform the procedures as described in subclause 5.6.1.6. Then if the UE is in the same selected PLMN where the last service request was attempted, the UE shall:

a) inform the upper layers. This could result in the UE attempting a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229 [13D] that can result in the emergency call being attempted to another IP-CAN; or

b) detach locally, if not detached already, attempt EPS attach for emergency bearer services.[TS 22.101 clause 10.1.1]

The ME shall identify an emergency number dialled by the end user as a valid emergency number and initiate emergency call establishment if it occurs under one or more of the following conditions. If it occurs outside of the following conditions, the ME should not initiate emergency call establishment but normal call establishment. Emergency number identification takes place before and takes precedence over any other (e.g. supplementary service related) number analysis.

a) 112 and 911 shall always be available. These numbers shall be stored on the ME.

b) Any emergency call number stored on a SIM/USIM when the SIM/USIM is present.

c) 000, 08, 110, 999, 118 and 119 when a SIM/USIM is not present. These numbers shall be stored on the ME.

d) Additional emergency call numbers that may have been downloaded by the serving network when the SIM/USIM is present.

11.2.6.3 Test description

11.2.6.3.1 Pre-test conditions

System Simulator:

– Cell A is set to ”Serving cell”;

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

– Cell E is set to ”Non-Suitable cell”.

– 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: 117, 144

– The following EN are configured as permanent EN on the UE: 112, 911, 000, 08, 110, 999, 118 and 119 (see TS 22.101 clause 10.1.1).

Preamble:

– the UE is in state Registered, Idle Mode (state 2) on Cell A according to TS 36.508 [18].

– During the attach the ATTACH ACCEPT message provides Local Emergency Numbers List. The local emergency number list is different from all emergency numbers stored in the USIM AND any emergency number stored permanently in the UE.

11.2.6.3.2 Test procedure sequence

Table 11.2.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

–

The following messages are sent and shall be received on Cell A.

–

–

–

–

1

Cause the UE to start a "call" using one of the Emergency Numbers stored on the USIM.

–

–

–

–

2

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

–>

RRC: RRCConnectionRequest

1

P

3-3L

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. The registration expiry time is set to 30s

–

–

–

–

4

The SS waits 1 second.

–

–

–

–

5

Release IMS Call (see Note 2).

–

–

–

–

5A

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

–

–

5B

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

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

–

6

The SS releases the RRC connection.

–

–

–

–

6A

The SS waits for the above expiration interval to elapse.

–

–

–

–

7

Cause the UE to start a "call" using one of the Emergency Numbers received in the ATTACH ACCEPT message IE Local Emergency Numbers List sent in the preamble. (Note 1)

–

–

–

–

8

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

–>

RRC: RRCConnectionRequest

4

P

9-9L

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 The registration expiry time is set to 30s

–

–

–

–

10

The SS waits 1 second.

–

–

–

–

11

Release IMS Call (see Note 2).

–

–

–

–

11A

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

–

–

11B

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

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

–

12

The SS releases the RRC connection.

–

–

–

–

12A

The SS waits for the above expiration interval to elapse.

–

–

–

–

13

The SS configures:

– Cell A as the "Non-Suitable cell".

– Cell C as a "Serving cell".

–

–

–

–

–

The following messages are sent and shall be received on Cell C.

–

–

–

–

14

The UE transmits a TRACKING AREA UPDATE REQUEST message.

–>

TRACKING AREA UPDATE REQUEST

–

–

15

The SS transmits a TRACKING AREA UPDATE ACCEPT message including IE Local Emergency Numbers List with 10 numbers different to the numbers stored on the USIM and those provided in the ATTACH ACCEPT in the preamble.

<–

TRACKING AREA UPDATE ACCEPT

–

–

16

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

–>

TRACKING AREA UPDATE COMPLETE

–

–

17

The SS releases the RRC connection.

–

–

–

–

18

Cause the UE to start a "call" using one of the Emergency Numbers which the SS sent in the ATTACH ACCEPT message IE Local Emergency Numbers List in the preamble (Note 1). The UE is expected to have them deleted (Note 3).

–

–

–

19

Check: Does UE transmit an RRCConnectionRequest message with establishmentCause set to ‘mo-Data"?

–>

RRC: RRCConnectionRequest

2

P

20

Void

–

–

–

–

20A-20I

Steps 3-14 from the Generic Test Procedure for IMS MO speech call as described in 36.508 Table 4.5A.6.3-1 take place (Note 4).

–

–

–

–

21

Void

–

–

–

–

21A

The SS waits 1 second.

–

–

–

–

22

Void

–

–

–

–

22A

Release IMS Call (Note 2).

–

–

–

–

22B

Void

–

–

–

–

22C

Void

–

–

–

–

23

The SS releases the RRC connection.

–

–

–

–

–

EXCEPTION: Steps 24 to 29A are repeated 10 times – each time with a different call number from one of the Emergency Numbers provided in the TRACKING AREA UPDATE ACCEPT message in step 15.

–

–

–

–

24

Cause the UE to start a "call" using one of the Emergency Numbers received in the TRACKING AREA UPDATE ACCEPT message in step 15. (Note 1)

–

–

–

–

25

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

–>

RRCConnectionRequest

2

P

26-26L

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. The registration expiry time is set to 30s

–

–

–

–

27

The SS waits 1 second.

–

–

–

–

28

Release IMS Call (Note 2).

–

–

–

–

28A

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

–

–

28B

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

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

–

29

The SS releases the RRC connection.

–

–

–

–

29A

The SS waits for the above expiration interval to elapse.

–

–

–

–

30

The SS configures:

– Cell C as the "Non-Suitable cell".

– Cell E as a "Serving cell".

–

–

–

–

–

The following messages are sent and shall be received on Cell E.

–

–

–

–

31

The UE transmits a TRACKING AREA UPDATE REQUEST message.

–>

TRACKING AREA UPDATE REQUEST

–

–

32

The SS transmits a TRACKING AREA UPDATE ACCEPT message which does not include IE Local Emergency Numbers List.

<–

TRACKING AREA UPDATE ACCEPT

–

–

33

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

–>

TRACKING AREA UPDATE COMPLETE

–

–

34

The SS releases the RRC connection.

–

–

–

–

EXCEPTION: Step 34a1

describes optional behaviour that depends on

the UE capability.

–

–

–

–

34a1

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.

–

–

–

–

35

Void

–

–

–

–

36

Void

–

–

–

–

37

Void

–

–

–

–

37A-37I

Void

–

–

–

–

38

Void

–

–

–

–

38A

Void

–

–

–

–

39

Void

–

–

–

–

39A

Void

–

–

–

–

39B

Void

–

–

–

–

39C

Void

–

–

–

–

40

Void

–

–

–

–

41

Cause the UE to start a "call" using one of the Emergency Numbers stored on the USIM.

–

–

–

–

42

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

–>

RRC: RRCConnectionRequest

3

P

43-55

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 The registration expiry time is set to 30s.

–

–

–

–

56

The SS waits 1 second.

–

–

–

–

57

Release IMS Call (see Note 2).

–

–

–

–

57A

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

–

–

57B

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

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

–

58

The SS releases the RRC connection.

–

–

–

–

–

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: This could be done by e.g. MMI or by AT command.

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

Note 3: The Local Emergency Numbers List stored in the user equipment is replaced by the contents of the new Emergency Number List IE.

Note 4: The Request-URI in the INVITE for MO Call Setup shall not be checked as according to the test purpose it has different values than specified in A.2.1 of TS 34.229-1 [35].

11.2.6.3.3 Specific message contents

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

Derivation path: 36.508 table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

Emergency number list

2 numbers: 115, 116

TS 24.008, 10.5.3.13

Numbers different to any emergency number stored permanently in the ME AND the numbers stored in the USIM, as indicated in TS 22.101 clause 10.1.1 a)-c).

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.6.3.3-2: Message RRCConnectionRequest (steps 2, 8, 25, 42 Table 11.2.6.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.6.3.3-3: Void

Table 11.2.6.3.3-4: Message TRACKING AREA UPDATE ACCEPT (step 15, Table 11.2.6.3.2-1)

Derivation path: 36.508 table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Emergency number list

10 numbers: 120 … 129 TS 24.008, 10.5.3.13

Numbers different to any emergency number stored permanently in the ME AND the numbers stored in the USIM, as indicated in TS 22.101 clause 10.1.1 a)-c) AND the numbers provided in ATTACH ACCEPT in Table 11.2.6.3.3-1.

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.6.3.3-5: Message RRCConnectionRequest (steps 19, 36 Table 11.2.6.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

mo-Data

}

}

}

Table 11.2.6.3.3-6: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 5A, 11A, 28A, 57A Table 11.2.6.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

00100100

regular deactivation