11.2.5 Emergency bearer services / Normal cell / NORMAL-SERVICE / Local Emergency Numbers List NOT sent in the Attach / PDN connect new emergency EPS bearer context / Authentication SQN code failure – MME aborts authentication continues using current security context / Service request

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

(1)

with { UE is in state Registered, Idle mode }

ensure that {

when { the UE is triggered to originate an emergency bearer service }

then { the UE sends a SERVICE REQUEST message }

}

(2)

with { UE in EMM-REGISTERED state and EMM-IDLE mode }

ensure that {

when { UE originates an emergency bearer service }

then { the UE sends a PDN connectivity request message without an APN }

}

(3)

with { UE having started an IMS Emergency call establishment when in EUTRA Normal Service }

ensure that {

  when { the UE indicates an Authentication failure and the MME continues using current security context }

    then { the UE is able to continue with the establishment of the IMS call }

            }

(4)

with { UE has sent a PDN CONNECTIVITY REQUEST message }

ensure that {

when { UE receives an RRCConnectionReconfiguration message including an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with IE Procedure transaction identity matching the PDN CONNECTIVITY REQUEST message and an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message linked to the EPS bearer context activated in the first message}

then { UE transmits an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message both containing the EPS bearer identity and enters EMM-REGISTERED state }

}

(5)

with { UE has a PDN connection for emergency bearer services and a PDN connection for non-emergency bearer services and the timer T3420 is running following a failed authentication procedure }

ensure that {

when { the timer T3420 expires at the UE }

then { the UE deactivates all non-emergency EPS bearer contexts }

}

11.2.5.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 24.301, clauses5.4.2.7, and 6.5.1.2.

[TS 24.301, clause 5.4.2.7]

…

For items c, d, and e:

Depending on local requirements or operator preference for emergency bearer services, if the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services, the MME need not follow the procedures specified for the authentication failure specified in the present subclause. The MME may respond to the AUTHENTICATION FAILURE message by initiating the security mode control procedure selecting the "null integrity protection algorithm" EIA0, null ciphering algorithm or may abort the authentication procedure and continue using the current security context, if any. The MME shall deactivate all non-emergency EPS bearer contexts, if any, by initiating an EPS bearer context deactivation procedure. The network shall consider the UE to be attached for emergency bearer services only.

If a UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services and sends an AUTHENTICATION FAILURE message to the MME with the EMM cause appropriate for these cases (#20, #21, or #26, respectively) and receives the SECURITY MODE COMMAND message before the timeout of timer T3418 or T3420, the UE shall deem that the network has passed the authentication check successfully, stop timer T3418 or T3420, respectively, and execute the security mode control procedure.

If a UE has a PDN connection for emergency bearer services established when timer T3418 or T3420 expires, the UE shall not deem that the network has failed the authentication check and not behave as described in item f. Instead the UE shall continue using the current security context, if any, deactivate all non-emergency EPS bearer contexts, if any, by initiating UE requested PDN disconnect procedure and consider itself to be attached for emergency bearer services only.

[TS 24.301, clause 6.5.1.2]

When the PDN CONNECTIVITY REQUEST message is sent together with an ATTACH REQUEST message, the UE shall not include the APN.

NOTE 1: If the UE needs to provide protocol configuration options which require ciphering or provide an APN, or both, during the attach procedure, the ESM information transfer flag is included in the PDN CONNECTIVITY REQUEST. The MME then at a later stage in the PDN connectivity procedure initiates the ESM information request procedure in which the UE can provide the MME with protocol configuration options or APN or both.

In order to request connectivity to a PDN using the default APN, the UE includes the Access point name IE in the PDN CONNECTIVITY REQUEST message or, when applicable, in the ESM INFORMATION RESPONSE message, according to the following conditions:

– if use of a PDN using the default APN requires PAP/CHAP, then the UE should include the Access point name IE; and

– in all other conditions, the UE need not include the Access point name IE.

In order to request connectivity to an additional PDN, the UE shall send a PDN CONNECTIVITY REQUEST message to the MME, start timer T3482 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.1.2.1). If the additional PDN connection is for emergency bearer services, the UE shall not include an APN in the PDN CONNECTIVITY REQUEST message; otherwise the UE shall include the requested APN.

In the PDN type information element the UE shall indicate the IP version capability of the IP stack associated with the UE as specified in subclause 6.4.1.

The UE shall set the request type to "initial request" when the UE is establishing a new PDN connectivity to a PDN in an attach procedure or in a stand-alone PDN connectivity procedure. The UE shall set the request type to "emergency" when the UE is requesting PDN connectivity for emergency bearer services for the first time. The UE shall set the request type to "handover" when the connectivity to a PDN is established upon handover from a non-3GPP access network and the UE was connected to that PDN before the handover to the 3GPP access network.

NOTE 2: For emergency bearer services, the handover from non-3GPP access to E-UTRA is not supported.

If the UE supports DSMIPv6, the UE may include a request for obtaining the IPv6 address and optionally the IPv4 address of the home agent in the Protocol configuration options IE in the PDN CONNECTIVITY REQUEST message. The UE may also include a request for obtaining the IPv6 Home Network Prefix. The UE shall request the IPv6 Home Network Prefix only if the UE has requested the home agent IPv6 address. The requested home agent address(es) and the Home Network Prefix are related to the APN the UE requested connectivity for.

The UE may set the ESM information transfer flag in the PDN CONNECTIVITY REQUEST message to indicate that it has ESM information, i.e. protocol configuration options, APN, or both, that needs to be sent after the NAS signalling security has been activated between the UE and the MME.

If the UE supports A/Gb mode or Iu mode, the UE shall indicate the support of the network requested bearer control procedures (see 3GPP TS 24.008 [13]) in A/Gb mode or Iu mode in the Protocol configuration options IE.

Protocol configuration options provided in the ESM INFORMATION RESPONSE message replace any protocol configuration options provided in the PDN CONNECTIVITY REQUEST message.

Figure 6.5.1.2.1: UE requested PDN connectivity procedure

11.2.5.3 Test description

11.2.5.3.1 Pre-test conditions

System Simulator:

– Cell A (PLMN1) is configured according to Table 6.3.2.2-1 in [18].

UE:

– None.

Preamble:

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

11.2.5.3.2 Test procedure sequence

Table 11.2.5.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-3

Steps 1 to 3 of the generic test procedure for IMS Emergency call establishment in EUTRA: Normal Service (TS 36.508 subclause 4.5A.4.3-1).

–

–

–

–

4

Check: Does the UE transmit an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and to initiate the session management procedure by including the SERVICE REQUEST message.

–>

SERVICE REQUEST

1

P

5

The SS transmits an AUTHENTICATION REQUEST message to initiate the EPS authentication and AKA procedure.

<–

AUTHENTICATION REQUEST

–

–

6

The UE transmits an AUTHENTICATION FAILURE message with EMM cause #21 "synch failure".

–>

AUTHENTICATION FAILURE

3

P

7

Void

–

–

–

–

8

Void

–

–

–

–

9-12

Steps 5 to 8 of the generic test procedure for IMS Emergency call establishment in EUTRA: Normal Service (TS 36.508 subclause 4.5A.4.3-1).

–

–

–

–

13

Check: Does the UE transmit a PDN CONNECTIVITY REQUEST message as specified to request an emergency PDN using current security context i.e. it is integrity protected and ciphered?

–>

PDN CONNECTIVITY REQUEST

2,3

P

14-18

Steps 10 to14 of the generic test procedure for IMS Emergency call establishment in EUTRA: Normal Service (TS 36.508 4.5A.4.3-1).

–

–

–

–

19

Check: Does the UE transmit an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message for the additional dedicated EPS Bearer?

–>

ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT

4

P

19A

Check : Does the UE transmit a PDN DISCONNECT REQUEST 15 seconds (T3420) after step 6?

–>

PDN DISCONNECT REQUEST

5

P

19B

Void

–

–

–

–

19C

Void

–

–

–

–

19D

The SS transmits a DEACTIVATE EPS BEARER CONTEXT REQUEST including the EPS bearer identity in the PDN DISCONNECT REQUEST sent by UE at step 19A.

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

–

–

19E

The UE transmits a DEACTIVATE EPS BEARER CONTEXT ACCEPT

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

–

20

Release IMS Call (see Note 1)

–

–

–

–

20A

Void

–

–

–

–

20B

Void

–

–

–

–

–

EXCEPTION: Steps 20Ca1 to 20Cb2 describe behaviour that depends on the UE implementation; the “lower case letters” identify alternative step sequences that take place depending on the UE behaviour.

–

–

–

–

20Ca1

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 from step 20.

–>

DETACH REQUEST

–

–

20Ca2

The SS responds the DETACH ACCEPT message.

<–

DETACH ACCEPT

–

–

20Cb1

If the UE does not transmit DETACH REQUEST within 5 seconds from step 20 the SS initiates Detach procedure with the Detach Type IE "re-attach not required".

<–

DETACH REQUEST

–

–

20Cb2

The UE sends DETACH ACCEPT message.

–>

DETACH ACCEPT

–

–

21

The SS releases the RRC connection.

–

–

–

–

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

Table 11.2.5.3.2-2: Void

11.2.5.3.3 Specific message contents

Table 11.2.5.3.3-1: Void

Table 11.2.5.3.3-2: Void

Table 11.2.5.3.3-3: Void

Table 11.2.5.3.3-4: Message AUTHENTICATION REQUEST(step5, Table11.2.5.3.2-1)

Derivation Path: 36.508 Table 4.7.2-7

Information Element

Value/remark

Comment

Condition

Authentication parameter AUTN (EPS challenge)

The SQN is out of correct range(SEQ – SEQMS > Δ).

Table 11.2.5.3.3-5: Message PDN CONNECTIVITY REQUEST (step13, Table11.2.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

Request type

‘0100’B

emergency

Access point name

Not present

Table 11.2.5.3.3-6: Message DEACTIVATE EPS BEARER CONTEXT REQUEST (step 19B , Table 11.2.5.3.2-1)

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

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

Default EBId-1

Same value as in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST of preamble

ESM cause

00100100

regular deactivation

Table 11.2.5.3.3-7: Message PDN DISCONNECT REQUEST (step 19A, Table 11.2.5.3.2-1)

Derivation Path: TS 36.508 Table 4.7.3-22

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

Linked EPS bearer identity

5

The default EPS bearer established in the preamble

Table 11.2.5.3.3-8: Message DETACH REQUEST (step 20Cb1, Table 11.2.5.3.2-1)

Derivation path: 36.508 table 4.7.2-12

Information Element

Value/Remark

Comment

Condition

Detach type

‘010’B

"re-attach not required"

EMM cause

‘07’H

EPS services not allowed