4.9.11 Test procedure for IMS Emergency call or eCall over IMS establishment in 5GC with IMS emergency registration

38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification

4.9.11.1 Scope

This procedure aims at verifying the UE establishment of IMS Emergency call or an eCall in 5GC when the UE is in 5GMM-IDLE and when IMS emergency registration is required e.g. under Normal Service conditions.

The procedure provides different emergency or eCall establishment options based on the condition parameters defined in Table 4.9.11.1-1.

Table 4.9.11.1-1: Condition parameters

Condition

Explanation

emergency call

When this parameter is present the TC has triggered the UE to initiate an emergency call. (NOTE)

eCall

When this parameter is present the TC has triggered the UE to initiate an eCall.

NOTE: If this generic procedure is referred in test case without any condition, emergency call shall be used as default.

The trigger to initiate MO call will be part of test case from where the generic procedure is called.

4.9.11.2 Procedure description

4.9.11.2.1 Initial conditions

System Simulator:

– 1 NR Cell connected to 5GC, default parameters.

User Equipment:

– The Test UICC shall be inserted. It shall provide Emergency Numbers.

The procedure assumes that the UE is in test state 1N-A, subclause 4.4A.2 on the NR Cell. All necessary details required shall be explicitly specified in the TC which calls the procedure in its entirety or refers to parts of it.

4.9.11.2.2 Procedure sequence

Table 4.9.11.2.2-1: Test procedure sequence UE IMS Emergency call or eCall over IMS establishment in 5GC with IMS emergency registration

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

EXCEPTION: Unless otherwise stated all the messages below are transmitted on the cell specified in the test case.

1

The UE transmits an RRCSetupRequest message with ‘establishmentCause’ set to ’emergency’.

–>

NR RRC: RRCSetupRequest

P

2

The SS transmits an RRCSetup message.

<–

NR RRC: RRCSetup

3

The UE transmits an RRCSetupComplete message and a SERVICE REQUEST message with ‘Service type’ set to ’emergency services’.

–>

NR RRC: RRCSetupComplete

5GMM: SERVICE REQUEST

P

4

The SS transmits a SecurityModeCommand message.

<–

NR RRC: SecurityModeCommand

5

The UE transmits a SecurityModeComplete message.

–>

NR RRC: SecurityModeComplete

6

The SS transmits an RRCReconfiguration message and a SERVICE ACCEPT message to establish SRB2 and DRB.

<–

NR RRC: RRCReconfiguration

5GMM: SERVICE ACCEPT

EXCEPTION: Depending upon UE implementation, steps 7 and 8 can occur in any order.

7

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

8

The UE transmits an UL NAS TRANSPORT message with ‘Request type’ set to ‘initial emergency request’, and, a PDU SESSION ESTABLISHMENT REQUEST.

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT REQUEST

P

EXCEPTION: In parallel to the events described in steps 9-10 below the events specified in steps 1a1 to 2 of Table 4.9.11.2.2-2 take place.

9

The SS transmits an RRCReconfiguration message and an PDU SESSION ESTABLISHMENT ACCEPT.

<–

NR RRC: RRCReconfiguration

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT ACCEPT

10

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

EXCEPTION: In parallel to the events described in steps 11-13 below the events specified in steps 3 of Table 4.9.11.2.2-2 take place.

11

The SS transmits an RRCReconfiguration message and an PDU SESSION MODIFICATION COMMAND.

<–

NR RRC: RRCReconfiguration

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION MODIFICATION COMMAND

EXCEPTION: Depending upon UE implementation, steps 12 and 13 can occur in any order.

12

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

13

The UE transmits an ULInformationTransfer message and an PDU SESSION MODIFICATION COMPLETE message.

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION MODIFICATION COMPLETE

P

Table 4.9.11.2.2-2: IMS signalling and Emergency call establishment

St

Procedure

Message Sequence

TP

Verdict

U – S

Message/PDU/SDU

EXCEPTION: Step 1a1 describes behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action.

1a1

The generic procedure for IP address allocation in the user plane specified in subclause 4.5A.3 takes place.

2

Generic Test Procedure for IMS Emergency registration / 5GS as defined in TS 34.229-5 [47], annex A.3 is performed.

EXCEPTION: Steps 3a1-3b1 describe a step sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value.

3a1

IF ‘emergency call’ THEN Generic test procedure for setting up IMS Emergency Voice Call / 5G as defined in TS 34.229-5 [47], annex A.6 is performed.

3b1

IF ‘eCall’ THEN Generic test procedure for NR eCall Setup and MSD Update, steps 1-3, as defined in Annex A.23 of TS 34.229-5 [47] is performed.

4.9.11.2.3 Specific Message content

All specific message contents shall be according subclause 4.6 and 4.7 with the exceptions below.

Table 4.9.11.2.3-1: SIB1 (at any time prior and during the procedure, Table 4.9.11.2.2-1)

Derivation Path: Table 4.6.1-28.

Information Element

Value/remark

Comment

Condition

SIB1 ::= SEQUENCE {

ims-EmergencySupport

Present

true

}

Table 4.9.11.2.3-2: RRCSetupRequest (step 1, Table 4.9.11.2.2-1)

Derivation Path: Table 4.6.1-23.

Information Element

Value/remark

Comment

Condition

RRCSetupRequest ::= SEQUENCE {

rrcSetupRequest SEQUENCE {

establishmentCause

emergency

}

}

Table 4.9.11.2.3-3: SERVICE REQUEST (step 3, Table 4.9.11.2.2-1)

Derivation Path: Table 4.7.1-16.

Information Element

Value/remark

Comment

Condition

Service type

‘0011’B

emergency services

Table 4.9.11.2.3-4: UL NAS TRANSPORT (step 8, Table 4.9.11.2.2-1)

Derivation Path: Table 4.7.1-10, condition INITIAL_PDU_REQUEST.

Information Element

Value/remark

Comment

Condition

Request type

‘011’B

initial emergency request

S-NSSAI

Not Present

DNN

Not Present

Table 4.9.11.2.3-5: PDU SESSION ESTABLISHMENT REQUEST (step 8, Table 4.9.11.2.2-1)

Derivation Path: Table 4.7.2-1.

Information Element

Value/remark

Comment

Condition

PDU session ID

A value that is not currently being used by another PDU session

PTI

A value currently not used

SSC mode

‘001’B

SSC mode 1

Table 4.9.11.2.3-6: DL NAS TRANSPORT (step 9, Table 4.9.11.2.2-1)

Derivation Path: Table 4.7.1-11, condition 5GSM_MESSAGE.

Table 4.9.11.2.3-7: PDU SESSION ESTABLISHMENT ACCEPT (step 9, Table 4.9.11.2.2-1)

Derivation Path: Table 4.7.2-2.

Information Element

Value/remark

Comment

Condition

Selected SSC mode

‘001’B

SSC mode 1

Authorized QoS rules

Reference QoS rule #2 as defined in Table 4.8.2.1-2.

Authorized QoS flow descriptions

Reference QoS flow #2 as defined in Table 4.8.2.3-2.

DNN

Not Present

Table 4.9.11.2.3-8: RRCReconfiguration (step 9, Table 4.9.11.2.2-1)

Derivation Path: Table 4.8.1-1: RRCReconfiguration-DRB (1, 0)

Table 4.9.11.2.3-9: PDU SESSION MODIFICATION COMMAND (step 11, Table 4.9.11.2.2-1)

Derivation Path: Table 4.7.2-2.

Information Element

Value/remark

Comment

Condition

PDU session ID

Same value as sent in PDU SESSION ESTABLISHMENT REQUEST message.

Authorized QoS rules

Reference QoS rule #7 as defined in Table 4.8.2.1-7 using condition IMS_VOICE.

Authorized QoS flow descriptions

Reference QoS flow #5 as defined in Table 4.8.2.3-5.

Table 4.9.11.2.3-10: RRCReconfiguration (step 11, Table 4.9.11.2.2-1)

Derivation Path: 4.8.1-1C RRCReconfiguration-Speech

Table 4.9.11.2.3-11: INVITE (step 3a1, Table 4.9.11.2.2-2)

Derivation Path: TS 34.229-5 [47], Annex A.6, Step 1 with conditions A7 and A28