11.4 Emergency Services

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

11.4.1 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call / Utilising emergency number stored on the USIM / New emergency PDU session / Network failing the authentication check (5G AKA)

11.4.1.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode }

ensure that {

when { UE is requested to make an outgoing call using an emergency number stored on the USIM }

then { UE establishes an RRC connection with the RRC establishmentCause set to "emergency", and, sends a SERVICE REQUEST message with Service type IE set to "emergency services", and, establishes a New emergency PDU session by sending an UL NAS TRANSPORT message with Request type set to "initial emergency request" and a PDU SESSION ESTABLISHMENT REQUEST }

}

(2)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-CONNECTED mode having established an Emergency call }

ensure that {

when { UE establishes that the network has failed the authentication check during a 5G AKA based primary authentication and key agreement procedure }

then { UE continues using the current security context, and, releases all non-emergency PDU sessions by initiating UE-requested PDU session release procedure and does not treat the active cell as barred for non-emergency services }

}

11.4.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [12], subclause 5.3.3.3, TS 24.501 [22], subclauses 5.6.1.2, 6.4.1.2, 5.4.1.3.7, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, subclause 5.3.3.3]

The UE shall set the contents of RRCSetupRequest message as follows:

…

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCSetupRequest message to lower layers for transmission.

[TS 24.501, subclause 5.6.1.2]

The UE initiates the service request procedure by sending a SERVICE REQUEST message to the AMF and starts timer T3517.

If the UE is sending the SERVICE REQUEST message from 5GMM-IDLE mode and the UE needs to send non-cleartext IEs, the UE shall send the SERVICE REQUEST message including the NAS message container IE as described in subclause 4.4.6.

…

For case c) in subclause 5.6.1.1, the Uplink data status IE shall not be included in the SERVICE REQUEST message except if the UE has one or more active always-on PDU sessions associated with the access type over which the SERVICE REQUEST message is sent. If the UE is not a UE configured for high priority access in selected PLMN and:

a) if the SERVICE REQUEST message is triggered by a request for emergency services from the upper layer, the UE shall set the service type IE in the SERVICE REQUEST message to "emergency services"; or

[TS 24.501, subclause 6.4.1.2]

In order to initiate the UE-requested PDU session establishment procedure, the UE shall create a PDU SESSION ESTABLISHMENT REQUEST message.

NOTE 0: When IMS voice is available over either 3GPP access or non-3GPP access, the "voice centric" UE in 5GMM-REGISTERED state will receive a request from upper layers to establish the PDU session for IMS signalling, if the conditions for performing an initial registration with IMS indicated in 3GPP TS 24.229 [14] subclause U.3.1.2 are satisfied.

If the UE requests to establish a new PDU session, the UE shall allocate a PDU session ID which is not currently being used by another PDU session over either 3GPP access or non-3GPP access.

The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION ESTABLISHMENT REQUEST message to the allocated PTI value.

…

If the UE requests to establish a new emergency PDU session, the UE shall set the SSC mode IE of the PDU SESSION ESTABLISHMENT REQUEST message to "SSC mode 1".

…

The UE shall transport:

a) the PDU SESSION ESTABLISHMENT REQUEST message;

b) the PDU session ID of the PDU session being established, or being handed over or being transferred;

..

e) the request type which is set to:

…

3) "initial emergency request", if the UE requests to establish a new emergency PDU session; and

…

If the request type is set to "initial emergency request" or "existing emergency PDU session", neither DNN nor S-NSSAI is transported by the UE using the NAS transport procedure as specified in subclause 5.4.5.

[TS 22.101, subclause 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.

…

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

[TS 24.501, subclause 5.4.1.3.7]

g) Network failing the authentication check.

If the UE deems that the network has failed the authentication check, then it shall request RRC to locally release the RRC connection and treat the active cell as barred (see 3GPP TS 38.304 [28]). The UE shall start any retransmission timers (e.g. T3510, T3517 or T3521), if they were running and stopped when the UE received the first AUTHENTICATION REQUEST message containing an incorrect authentication challenge data causing authentication failure.

…

For items c, d, e, and f whether or not the UE is registered for emergency services:

…

The UE shall deem that the network has failed the authentication check or assume that the authentication is not genuine and proceed as described in item g above if any of the following occurs:

– the timer T3520 expires;

…

For items c, d, e, and f:

…

If a UE has an emergency PDU session established or is establishing an emergency PDU session when timer T3520 expires, the UE shall not deem that the network has failed the authentication check and not behave as described in item g. Instead the UE shall continue using the current security context, if any, release all non-emergency PDU sessions, if any, by initiating UE-requested PDU session release procedure. If there is an ongoing PDU session establishment procedure, the UE shall release all non-emergency PDU sessions upon completion of the PDU session establishment procedure. The UE shall start any retransmission timers (e.g. T3510, T3517 or T3521) if:

– they were running and stopped when the UE received the AUTHENTICATION REQUEST message and detected an authentication failure;

– the procedures associated with these timers have not yet been completed.

The UE shall behave as if the UE is registered for emergency services.

11.4.1.3 Test description

11.4.1.3.1 Pre-test conditions

System Simulator:

– 1 NR Cell

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport..

UE:

– The UE is equipped with a test USIM with USIM Configuration 20 as defined in TS 38.508-1 [4] Table 6.4.1-20 (USIM contains two Emergency Numbers: 144, 117).

Preamble:

– Cells power level configuration in accordance with TS 38.508-1 [4], Table 6.2.2.1-3:

– NR Cell 1 "Serving cell"

– The UE is in test state 1N-A as defined in TS 38.508-1 [4], subclause 4.4A.2 on NR Cell 1.

NOTE: pc_noOf_PDUsSameConnection + pc_noOf_PDUsNewConnection > 0.

11.4.1.3.2 Test procedure sequence

Table 11.4.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

–

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

–

–

–

–

1

Make the UE attempt an IMS emergency call dialling the number 144 which is stored on the USIM. (NOTE 1)

–

–

–

–

2

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

1

–

2A

The SS initiates the 5G AKA based primary authentication and key agreement procedure by sending an AUTHENTICATION REQUEST message; the included ngKSI value is the same as the one used in the initial message SERVICE REQUEST sent in step 2.

<–

AUTHENTICATION REQUEST

–

–

2B

The UE sends an AUTHENTICATION FAILURE message with 5GMM cause #71 "ngKSI already in use"

–>

AUTHENTICATION FAILURE

–

–

2BA

Wait for T3520 expires.

–

–

–

–

–

EXCEPTION: Depending on the number of non-IMS Emergency relevant PDUs active at this moment of time step 2C is repeated 1 or more times.

–

–

–

–

2C

FOR i=1 TO i= pc_noOf_PDUsSameConnection + pc_noOf_PDUsNewConnection

Repeat the PDU session release procedure specified in Table 11.4.1.3.2-2: Parallel behaviour.

Depending on UE implementation the PDU session release procedures can run in parallel or in sequence.

–

–

–

–

3

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

4

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

4A

Start Timer T1=5 seconds. NOTE: This is an arbitrary value to wait for UE to initiate deregistration.

–

–

–

–

–

EXCEPTION: Steps 4Ba1-4Bb1 describes optional behaviour that depends on the UE implementation.

–

–

–

–

4Ba1

The UE transmits a DEREGISTRATION REQUEST message with De-registration type IE set to “Normal de-registration”.

–>

NR RRC: ULInformationTransfer 5GMM: DEREGISTRATION REQUEST

–

–

4Ba2

The SS transmits a DEREGISTRATION ACCEPT message.

<–

NR RRC: DLInformationTransfer 5GMM: DEREGISTRATION ACCEPT

–

–

4Ba3

Stop Timer T1=5 seconds

–

–

–

–

4Bb1

Timer T1=5 seconds expires

–

–

–

–

5

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

5A

Start Timer T1=5 seconds.

–

–

–

–

EXCEPTION: Steps 5Aa1-5Ab3 describes optional behaviour that depends on the UE implementation.

–

–

–

–

5Aa1

Check: Does the UE transmit RRCSetupRequest on NR Cell 1?

–>

NR RRC: RRCSetupRequest

2

P

5Aa2

Stop Timer T1=5 seconds

–

–

–

–

5Aa3

Step 2-20a1 of Table 4.5.2.2- 2: Registration procedure for initial registration as specified in TS 38.508-1 [4] are performed on NR Cell 1.

–

–

–

–

5Aa4

Make the UE attempt an IMS [non-emergency] call. (NOTE 1)

–

–

–

–

5Ab1

Timer T1=5 seconds expires

–

–

–

–

5Ab2

Make the UE attempt an IMS [non-emergency] call. (NOTE 1)

5Ab3

Check: Does the UE perform on NR Cell 1 the Registration procedure for initial registration as specified in TS 38.508-1 [4] subclause 4.5.2.2- 2?

–>

NR RRC: RRCSetupRequest

2

P

6-9

Void

–

–

–

–

10-21b3

Step 2-13b3 of Table 4.9.15.2.2-1: IMS MO speech call establishment in 5GC as defined in TS 38.508-1 [4] are performed.

–

–

–

–

22

Table 4.9.18.2.2-1: IMS MT call release in 5GC as defined in TS 38.508-1 [4] is performed.

–

–

–

–

23

The SS transmits an RRCRelease message.

<–

NR RRC: RRCRelease

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

Table 11.4.1.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE transmit a PDU SESSION RELEASE REQUEST message with PDU session ID equal to one of the IDs of an existing PDU session BUT different to the PDU session ID assigned to the Emergency PDU session in step 2, Table 11.4.1.3.2-1?

–

PDU SESSION RELEASE REQUEST

2

P

2

Check: Does the UE perform PDU session release procedure defined in clause 4.9.21 of TS 38.508-1 [4]?

–

2

P

11.4.1.3.3 Specific message contents

Table 11.4.1.3.3-1: Message AUTHENTICATION REQUEST (step 2A, Table 11.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-1

Information Element

Value/Remark

Comment

Condition

ngKSI

The same ng-KSI assigned in the Preamble and indicated in the initial message SERVICE REQUEST sent in step 2

Table 11.4.1.3.3-2: Message AUTHENTICATION FAILURE (step 2B, Table 11.4.1.3.2-1)

Derivation path: TS 38.508-1 [4], Table 4.7.1-4

Information Element

Value/Remark

Comment

Condition

5GMM cause

‘0100 0111’B

ngKSI already in use

11.4.2 5GMM-DEREGISTERED.LIMITED-SERVICE / Emergency call / Utilisation of emergency numbers stored on the ME / Initial registration for emergency services / Handling of forbidden PLMNs

11.4.2.1 Test Purpose (TP)

(1)

with { UE in 5GMM-DEREGISTERED.LIMITED-SERVICE state }

ensure that {

when { UE is requested to make an outgoing call using an emergency number stored on the ME }

then { UE establishes an RRC connection with the RRC establishmentCause set to "emergency", and, attempts an Initial registration for emergency services by sending a REGISTRATION REQUEST message with IE Service type set to "emergency services", and, accepts and applies security with NULL security and integrity algorithms, and, after successful completion of the registration for emergency services establishes an emergency PDU session by sending an UL NAS TRANSPORT message with Request type set to "initial emergency request" and a PDU SESSION ESTABLISHMENT REQUEST }

}

(2)

with { UE in 5GMM-DEREGISTERED.LIMITED-SERVICE state }

ensure that {

when { UE has performed an IMS Emergency call on a forbidden PLMN }

then { UE does not remove the PLMN code of the accessed PLMN from the list of forbidden PLMNs }

}

11.4.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [12], subclause 5.3.3.3, TS 23.501 [37], subclause 5.16.4.1, TS 23.122 [38], subclauses 2, 3.1, 3.5, TS 24.501 [22], subclauses 4.4.4.1, 5.1.3.2.1.3.3, 5.3.2, 5.4.2.3, 5.5.1.2.2, 5.5.1.2.4, 6.4.1.2, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, subclause 5.3.3.3]

The UE shall set the contents of RRCSetupRequest message as follows:

…

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCSetupRequest message to lower layers for transmission.

[TS 23.501, subclause 5.16.4.1]

UEs that are in limited service state, as specified in TS 23.122 [17], or that camp normally on a cell but failed to register successfully to the network under conditions specified in TS 24.501 [47], initiate the Registration procedure by indicating that the registration is to receive Emergency Services, referred to as Emergency Registration, and a Follow-on request is included in the Registration Request to initiate PDU Session Establishment procedure with a Request Type indicating "Emergency Request". UEs that had registered for normal services and do not have emergency PDU Sessions established and that are subject to Mobility Restriction in the present area or RAT (e.g. because of restricted tracking area) shall initiate the UE Requested PDU Session Establishment procedure to receive Emergency Services, i.e. with a Request Type indicating "Emergency Request". Based on local regulation, the network supporting Emergency Services for UEs in limited service state provides Emergency Services to these UE, regardless whether the UE can be authenticated, has roaming or Mobility Restrictions or a valid subscription.

[TS 23.122, clause 2]

If the MS is unable to find a suitable cell to camp on, or the SIM is not inserted, or if it receives certain responses to an LR request (e.g., "illegal MS"), it attempts to camp on a cell irrespective of the PLMN identity, and enters a "limited service" state in which it can only attempt to make emergency calls. An MS operating in NB-S1 mode, never attempts to make emergency calls.

[TS 23.122, subclause 3.1]

An MS that is attaching for emergency bearer services or is attached for emergency bearer services may access PLMNs in the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service". The MS shall not remove any entry from the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service" as a result of such accesses.

[TS 23.122, subclause 3.5]

There are a number of situations in which the MS is unable to obtain normal service from a PLMN. These include:

a) Failure to find a suitable cell of the selected PLMN;

…

(In automatic PLMN selection mode, items a, c and f would normally cause a new PLMN selection, but even in this case, the situation may arise when no PLMNs are available and allowable for use).

For the items a to f, the MS attempts to camp on an acceptable cell, irrespective of its PLMN identity, so that emergency calls can be made if necessary, with the exception that an MS operating in NB-S1 mode, shall never attempt to make emergency calls. When in the limited service state with a valid SIM, the MS shall search for available and allowable PLMNs in the manner described in subclause 4.4.3.1 and when indicated in the SIM also as described in subclause 4.4.3.4. For an MS that is not in eCall only mode, with the exception of performing GPRS attach or EPS attach for emergency bearer services, or performing registration for emergency services, no LR requests are made until a valid SIM is present and either a suitable cell is found or a manual network reselection is performed. For an MS in eCall only mode, no LR requests are made except for performing EPS attach for emergency bearer services or registration for emergency services. When performing GPRS attach or EPS attach for emergency bearer services, or registration for emergency services, the PLMN of the current serving cell is considered as the selected PLMN for the duration the MS is attached for emergency bearer services or registered for emergency services. In the limited service state the presence of the MS need not be known to the PLMN on whose cell it has camped.

There are also other conditions under which only emergency calls may be made. These are shown in table 2 in clause 5. ProSe direct communication and ProSe direct discovery for public safety use can be initiated if necessary (see 3GPP TS 24.334 [51]) when in the limited service state due to items a) or c) or f). V2X communication over PC5 can be initiated if necessary (see 3GPP TS 24.386 [59]) when in the limited service state due to items a) or c) or f).

[TS 24.501, subclause 4.4.4.1]

The use of "null integrity protection algorithm" 5G-IA0 (see subclause 9.11.3.32) in the current 5G NAS security context is only allowed for an unauthenticated UE for which establishment of emergency services is allowed. For setting the security header type in outbound NAS messages, the UE and the AMF shall apply the same rules irrespective of whether the "null integrity protection algorithm" or any other integrity protection algorithm is indicated in the 5G NAS security context.

If the "null integrity protection algorithm"5G-IA0 has been selected as an integrity protection algorithm, the receiver shall regard the NAS messages with the security header indicating integrity protection as integrity protected.

[TS 24.501, subclause 5.1.3.2.1.3.3]

The substate 5GMM-DEREGISTERED.LIMITED-SERVICE is chosen in the UE, when it is known that a selected cell for 3GPP access or TA for non-3GPP access is unable to provide normal service (e.g. the selected cell over 3GPP access is in a forbidden PLMN or is in a forbidden tracking area or TA for non-3GPP access is forbidden).

[TS 24.501, subclause 5.3.2]

The UE provides the SUPI to the network in concealed form. The SUCI is a privacy preserving identifier containing the concealed SUPI. When the SUPI contains a network specific identifier, the SUCI shall take the form of an NAI as specified in 3GPP TS 23.003 [4].

A UE supporting N1 mode includes a SUCI:

a) in the REGISTRATION REQUEST message when the UE is attempting initial registration procedure and a valid 5G-GUTI is not available; or

…

The UE shall use the "null-scheme" as specified in 3GPP TS 33.501 [24] to generate the SUCI, if the following applies:

a) the UE performs a registration procedure for emergency services or initiates a de-registration procedure before the registration procedure for emergency services was completed successfully; and

[TS 24.501, subclause 5.4.2.3]

If the UE is registered for emergency services, performing initial registration for emergency services or establishing an emergency PDU session and the SECURITY MODE COMMAND message is received with ngKSI value "000" and 5G-IA0 and 5G-EA0 as selected 5G NAS security algorithms, the UE shall locally derive and take in use 5G NAS security context. The UE shall delete existing current 5G NAS security context.

The UE shall accept a SECURITY MODE COMMAND message indicating the "null integrity protection algorithm" 5G-EA0 as the selected 5G NAS integrity algorithm only if the message is received when the UE is registered for emergency services, performing initial registration for emergency services or establishing an emergency PDU session.

[TS 24.501, subclause 5.5.1.2.2]

The UE in state 5GMM-DEREGISTERED shall initiate the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF,

…

b) when the UE performs initial registration for emergency services;

…

If the UE initiates an initial registration for emergency services or needs to prolong the established NAS signalling connection after the completion of the initial registration procedure (e.g. due to uplink signalling pending), the UE shall set the Follow-on request indicator to 1.

[TS 24.501, subclause 5.5.1.2.4]

If the initial registration procedure is not for emergency services, and if the PLMN identity of the registered PLMN is a member of the list of "forbidden PLMNs", any such PLMN identity shall be deleted from the corresponding list(s).

[TS 24.501, subclause 6.4.1.2]

In order to initiate the UE-requested PDU session establishment procedure, the UE shall create a PDU SESSION ESTABLISHMENT REQUEST message.

NOTE 0: When IMS voice is available over either 3GPP access or non-3GPP access, the "voice centric" UE in 5GMM-REGISTERED state will receive a request from upper layers to establish the PDU session for IMS signalling, if the conditions for performing an initial registration with IMS indicated in 3GPP TS 24.229 [14] subclause U.3.1.2 are satisfied.

If the UE requests to establish a new PDU session, the UE shall allocate a PDU session ID which is not currently being used by another PDU session over either 3GPP access or non-3GPP access.

The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION ESTABLISHMENT REQUEST message to the allocated PTI value.

…

If the UE requests to establish a new emergency PDU session, the UE shall set the SSC mode IE of the PDU SESSION ESTABLISHMENT REQUEST message to "SSC mode 1".

…

The UE shall transport:

a) the PDU SESSION ESTABLISHMENT REQUEST message;

b) the PDU session ID of the PDU session being established, or being handed over or being transferred;

..

e) the request type which is set to:

…

3) "initial emergency request", if the UE requests to establish a new emergency PDU session; and

…

If the request type is set to "initial emergency request" or "existing emergency PDU session", neither DNN nor S-NSSAI is transported by the UE using the NAS transport procedure as specified in subclause 5.4.5.

[TS 22.101, subclause 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.

11.4.2.3 Test description

11.4.2.3.1 Pre-test conditions

System Simulator:

– 1 NR Cell

– NR Cell 1, as defined in TS 38.508-1 [4], Table 4.4.2-3, with the exception that cells’ PLMN is defined in Table 11.4.2.3.1-1 below.

Table 11.4.2.3.1-1: PLMN identifiers

NR Cell

PLMN name

1

PLMN2

– System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport.

UE:

– The UE is equipped with a test USIM with USIM Configuration 15 as defined in TS 38.508-1 [4], Table 6.4.1-15 (PLMN2 is set in it as ‘forbidden PLMN’, PLMN1 is the HPLMN).

Preamble:

– The UE is in test state 0N-B (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2. Prior to being switched off the UE is registered on PLMN1.

11.4.2.3.2 Test procedure sequence

Table 11.4.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

–

–

–

–

–

The SS configures:

– NR Cell 1 as "Serving cell"

–

–

–

–

2

Switch the UE on.

–

–

–

–

3

Make the UE attempt an IMS emergency call dialling a number which is stored on the ME (e.g. 112 or 911). (NOTE 1)

–

–

–

–

4

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment without IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.12?

–

–

1

–

5

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

6

Void

–

–

–

–

6A-6C

Steps 1-3 of the Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A

take place.

–

–

–

–

7

Start Timer T1=6 seconds.

NOTE: This is an arbitrary value to wait for UE initiated detach.

–

–

–

–

–

EXCEPTION: In parallel to step 8 below, the steps specified in Tables 11.4.2.3.2-2 and 11.4.2.3.2-3 may take place

–

–

–

–

8

Timer T1=5 seconds expires

–

–

–

–

8a1-8b3

Void

–

–

–

–

9

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

9A

Make the UE attempt an IMS none-emergency call. (NOTE 2).

–

–

–

–

10

Check: Does the UE transmit an RRCSetupRequest message in the next 10seconds?

NOTE: This is an arbitrary value to wait for catching not allowed UE behaviour.

–>

NR RRC: RRCSetupRequest

2

F

NOTE 1: This could be done by e.g. MMI or AT command.

NOTE 2: This could be done by e.g. MMI or AT command.

Table 11.4.2.3.2-2: Parallel Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a DEREGISTRATION REQUEST message with De-registration type IE set to "Normal de-registration".

–>

NR RRC: ULInformationTransfer

5GMM: DEREGISTRATION REQUEST

–

–

2

The SS transmits a DEREGISTRATION ACCEPT message.

<–

NR RRC: DLInformationTransfer

5GMM: DEREGISTRATION ACCEPT

–

–

Table 11.4.2.3.2-3: Parallel Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a PDU SESSION RELEASE REQUEST message.

–>

NR RRC: ULInformationTransfer

PDU SESSION RELEASE REQUEST

–

–

2

The SS transmits a PDU SESSION RELEASE COMMAND message.

<–

NR RRC: DLInformationTransfer NR NAS: PDU SESSION RELEASE COMMAND

–

–

3

Check: Does the UE transmit a PDU SESSION RELEASE COMPLETE message?

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION RELEASE COMPLETE

–

–

11.4.2.3.3 Specific message contents

Table 11.4.2.3.3-1: REGISTRATION REQUEST (step 4, Table 11.4.2.3.2-1; step 3, TS 38.508-1 [4], Table 4.9.12.2.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6, condition EMERGENCY.

Information Element

Value/remark

Comment

Condition

5GS mobile identity

SUCI

The UE shall use the "null-scheme" as specified in 3GPP TS 33.501 [20] to generate the SUCI

Table 11.4.2.3.3-2: DEREGISTRATION REQUEST (Step 8a1, Table 11.4.2.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-12, Condition NORMAL.

Table 11.4.2.3.3-3: Void

11.4.3 5GMM-DEREGISTERED.NO-SUPI / Emergency call / Utilisation of emergency numbers stored on the ME / Initial registration for emergency services

11.4.3.1 Test Purpose (TP)

(1)

with { UE in 5GMM-DEREGISTERED.NO-SUPI state (no USIM) }

ensure that {

when { UE is requested to make an outgoing call using an emergency number stored on the ME }

then { UE establishes an RRC connection with the RRC establishmentCause set to "emergency", and, attempts an Initial registration for emergency services by sending a REGISTRATION REQUEST message with IE Service type set to "emergency services", and, accepts and applies security with NULL security and integrity algorithms, and, after successful completion of the registration for emergency services establishes an emergency PDU session by sending an UL NAS TRANSPORT message with Request type set to "initial emergency request" and a PDU SESSION ESTABLISHMENT REQUEST }

}

11.4.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [12], subclause 5.3.3.3, TS 23.501 [37], subclause 5.16.4.1, TS 23.122 [38], subclauses 2, 3.5, TS 24.501 [22], subclauses 4.4.4.1, 5.1.3.2.1.3.6, 5.3.2, 5.4.2.3, 5.5.1.2.2, 6.4.1.2, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 36.331, subclause 5.3.3.3]

The UE shall set the contents of RRCSetupRequest message as follows:

…

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCSetupRequest message to lower layers for transmission.

[TS 23.501, subclause 5.16.4.1]

UEs that are in limited service state, as specified in TS 23.122 [17], or that camp normally on a cell but failed to register successfully to the network under conditions specified in TS 24.501 [47], initiate the Registration procedure by indicating that the registration is to receive Emergency Services, referred to as Emergency Registration, and a Follow-on request is included in the Registration Request to initiate PDU Session Establishment procedure with a Request Type indicating "Emergency Request". UEs that had registered for normal services and do not have emergency PDU Sessions established and that are subject to Mobility Restriction in the present area or RAT (e.g. because of restricted tracking area) shall initiate the UE Requested PDU Session Establishment procedure to receive Emergency Services, i.e. with a Request Type indicating "Emergency Request". Based on local regulation, the network supporting Emergency Services for UEs in limited service state provides Emergency Services to these UE, regardless whether the UE can be authenticated, has roaming or Mobility Restrictions or a valid subscription.

[TS 23.122, clause 2]

If the MS is unable to find a suitable cell to camp on, or the SIM is not inserted, or if it receives certain responses to an LR request (e.g., "illegal MS"), it attempts to camp on a cell irrespective of the PLMN identity, and enters a "limited service" state in which it can only attempt to make emergency calls. An MS operating in NB-S1 mode, never attempts to make emergency calls.

[TS 23.122, subclause 3.5]

There are a number of situations in which the MS is unable to obtain normal service from a PLMN. These include:

…

b) No SIM in the MS;

…

For the items a to f, the MS attempts to camp on an acceptable cell, irrespective of its PLMN identity, so that emergency calls can be made if necessary, with the exception that an MS operating in NB-S1 mode, shall never attempt to make emergency calls. When in the limited service state with a valid SIM, the MS shall search for available and allowable PLMNs in the manner described in subclause 4.4.3.1 and when indicated in the SIM also as described in subclause 4.4.3.4. For an MS that is not in eCall only mode, with the exception of performing GPRS attach or EPS attach for emergency bearer services, or performing registration for emergency services, no LR requests are made until a valid SIM is present and either a suitable cell is found or a manual network reselection is performed. For an MS in eCall only mode, no LR requests are made except for performing EPS attach for emergency bearer services or registration for emergency services. When performing GPRS attach or EPS attach for emergency bearer services, or registration for emergency services, the PLMN of the current serving cell is considered as the selected PLMN for the duration the MS is attached for emergency bearer services or registered for emergency services. In the limited service state the presence of the MS need not be known to the PLMN on whose cell it has camped.

There are also other conditions under which only emergency calls may be made. These are shown in table 2 in clause 5. ProSe direct communication and ProSe direct discovery for public safety use can be initiated if necessary (see 3GPP TS 24.334 [51]) when in the limited service state due to items a) or c) or f). V2X communication over PC5 can be initiated if necessary (see 3GPP TS 24.386 [59]) when in the limited service state due to items a) or c) or f).

[TS 24.501, subclause 4.4.4.1]

The use of "null integrity protection algorithm" 5G-IA0 (see subclause 9.11.3.32) in the current 5G NAS security context is only allowed for an unauthenticated UE for which establishment of emergency services is allowed. For setting the security header type in outbound NAS messages, the UE and the AMF shall apply the same rules irrespective of whether the "null integrity protection algorithm" or any other integrity protection algorithm is indicated in the 5G NAS security context.

If the "null integrity protection algorithm"5G-IA0 has been selected as an integrity protection algorithm, the receiver shall regard the NAS messages with the security header indicating integrity protection as integrity protected.

[TS 24.501, subclause 5.1.3.2.1.3.6]

The substate 5GMM-DEREGISTERED.NO-SUPI is chosen in the UE, if the N1 mode is enabled and the UE has no valid subscriber data available (SIM/USIM not available, the SIM/USIM is considered invalid by the UE).

[TS 24.501, subclause 5.3.2]

A UE supporting NG-RAN includes a PEI:

a) when neither SUPI nor valid 5G-GUTI is available to use for emergency services in the REGISTRATION REQUEST message with 5GS registration type IE set to "emergency registration"; and

[TS 24.501, subclause 5.4.2.3]

If the UE is registered for emergency services, performing initial registration for emergency services or establishing an emergency PDU session and the SECURITY MODE COMMAND message is received with ngKSI value "000" and 5G-IA0 and 5G-EA0 as selected 5G NAS security algorithms, the UE shall locally derive and take in use 5G NAS security context. The UE shall delete existing current 5G NAS security context.

The UE shall accept a SECURITY MODE COMMAND message indicating the "null integrity protection algorithm" 5G-EA0 as the selected 5G NAS integrity algorithm only if the message is received when the UE is registered for emergency services, performing initial registration for emergency services or establishing an emergency PDU session.

[TS 24.501, subclause 5.5.1.2.2]

The UE in state 5GMM-DEREGISTERED shall initiate the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF,

…

b) when the UE performs initial registration for emergency services;

…

If the UE initiates an initial registration for emergency services or needs to prolong the established NAS signalling connection after the completion of the initial registration procedure (e.g. due to uplink signalling pending), the UE shall set the Follow-on request indicator to 1.

[TS 24.501, subclause 6.4.1.2]

In order to initiate the UE-requested PDU session establishment procedure, the UE shall create a PDU SESSION ESTABLISHMENT REQUEST message.

NOTE 0: When IMS voice is available over either 3GPP access or non-3GPP access, the "voice centric" UE in 5GMM-REGISTERED state will receive a request from upper layers to establish the PDU session for IMS signalling, if the conditions for performing an initial registration with IMS indicated in 3GPP TS 24.229 [14] subclause U.3.1.2 are satisfied.

If the UE requests to establish a new PDU session, the UE shall allocate a PDU session ID which is not currently being used by another PDU session over either 3GPP access or non-3GPP access.

The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION ESTABLISHMENT REQUEST message to the allocated PTI value.

…

If the UE requests to establish a new emergency PDU session, the UE shall set the SSC mode IE of the PDU SESSION ESTABLISHMENT REQUEST message to "SSC mode 1".

…

The UE shall transport:

a) the PDU SESSION ESTABLISHMENT REQUEST message;

b) the PDU session ID of the PDU session being established, or being handed over or being transferred;

..

e) the request type which is set to:

…

3) "initial emergency request", if the UE requests to establish a new emergency PDU session; and

…

If the request type is set to "initial emergency request" or "existing emergency PDU session", neither DNN nor S-NSSAI is transported by the UE using the NAS transport procedure as specified in subclause 5.4.5.

[TS 22.101, subclause 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.

11.4.3.3 Test description

11.4.3.3.1 Pre-test conditions

System Simulator:

– 1 NR Cells

– NR Cell 1, as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport.

UE:

– The UE is NOT equipped with USIM.

Preamble:

– The UE is in test state 0-A (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.4.3.3.2 Test procedure sequence

Table 11.4.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Switch the UE on.

–

–

–

–

2

Make the UE attempt an IMS emergency call dialling a number which is stored on the ME (e.g. 112 or 911). (NOTE 1)

–

–

–

–

3

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment without IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.12?

–

–

1

P

4

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

5

Void

–

–

–

–

6A-6C

Steps 1-3 of the Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A take place.

–

–

–

–

6

Start Timer=5 sec.

NOTE: This is an arbitrary value to wait for UE initiated detach.

–

–

–

–

–

EXCEPTION: In parallel to step 7 below, the steps specified in Tables 11.4.3.3.2-2, and 11.4.3.3.2-3 may take place

–

–

–

–

7

Timer T1=5 seconds expires

–

–

–

–

8

The Generic test procedure Switch/Power off procedure after EMERGENCY CALL RELEASED in RRC_CONNECTED of Table 10.3.7-1 in TS 38.523-3 [3] takes place.

–

–

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

Table 11.4.3.3.2-2: Parallel Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a DEREGISTRATION REQUEST message with De-registration type IE set to "Normal de-registration".

–>

NR RRC: ULInformationTransfer

5GMM: DEREGISTRATION REQUEST

–

–

2

The SS transmits a DEREGISTRATION ACCEPT message.

<–

NR RRC: DLInformationTransfer

5GMM: DEREGISTRATION ACCEPT

–

–

Table 11.4.3.3.2-3: Parallel Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a PDU SESSION RELEASE REQUEST message.

–>

NR RRC: ULInformationTransfer

PDU SESSION RELEASE REQUEST

–

–

2

The SS transmits a PDU SESSION RELEASE COMMAND message.

<–

NR RRC: DLInformationTransfer NR NAS: PDU SESSION RELEASE COMMAND

–

–

3

Check: Does the UE transmit a PDU SESSION RELEASE COMPLETE message?

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION RELEASE COMPLETE

–

–

11.4.3.3.3 Specific message contents

Table 11.4.3.3.3-1: REGISTRATION REQUEST (step 3, Table 11.4.3.3.2-1; step 3, TS 38.508-1 [4], Table 4.9.12.2.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6, condition EMERGENCY.

Information Element

Value/remark

Comment

Condition

5GS mobile identity

PEI

Table 11.4.3.3.3-2: DEREGISTRATION REQUEST (Step 7a1, Table 11.4.3.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-12, Condition NORMAL.

11.4.4 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE T3346 running / Emergency call establishment / 5GMM-REGISTERED.NORMAL-SERVICE / Emergency call establishment before T3396 expiry

11.4.4.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state, timer T3346 is running and 5GMM-IDLE mode }

ensure that {

when { UE is requested to make an Emergency call }

then { UE initiates the registration procedure for mobility and periodic registration update, and, establishes the Emergency call }

}

(2)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state, timer T3396 is running and 5GMM-IDLE mode }

ensure that {

when { UE is requested to make an Emergency call }

then { UE establishes the Emergency call }

}

11.4.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501 [22], subclause 5.5.1.3.5, 5.3.9, 5.5.1.3.2, 6.3.3.3, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, subclause 5.5.1.3.5]

If the mobility and periodic registration update request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

…

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

…

#22 (Congestion).

If the T3346 value IE is present in the REGISTRATION REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.1.3.7.

The UE shall abort the registration procedure for mobility and periodic registration update. If the rejected request was not for initiating an emergency PDU session, the UE shall set the 5GS update status to 5U2 NOT UPDATED and change to state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE.

The UE shall stop timer T3346 if it is running.

If the REGISTRATION REJECT message is integrity protected, the UE shall start timer T3346 with the value provided in the T3346 value IE.

…

The UE stays in the current serving cell and applies the normal cell reselection process. The registration procedure for mobility and periodic registration update is started, if still necessary, when timer T3346 expires or is stopped.

[TS 24.501, subclause 5.3.9]

If timer T3346 is running or is deactivated, and the UE is a UE configured for high priority access in selected PLMN, or the UE needs to initiate signalling for emergency services or emergency services fallback, then the UE is allowed to initiate 5GMM procedures.

[TS 24.501, subclause 5.5.1.3.2]

The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the AMF,

…

k) when the UE in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE receives a request from the upper layers to establish an emergency PDU session or perform emergency services fallback;

[TS 24.501, subclause 6.3.3.3]

Upon receipt of a PDU SESSION RELEASE COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE considers the PDU session as released and the UE shall create a PDU SESSION RELEASE COMPLETE message.

…

If the PDU SESSION RELEASE COMMAND message includes 5GSM cause #26 "insufficient resources" and the Back-off timer value IE, the UE shall ignore the 5GSM congestion re-attempt indicator IE provided by the network, if any, and the UE shall take different actions depending on the timer value received for timer T3396 in the Back-off timer value:

…

When the timer T3396 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services.

…

The UE shall set the Follow-on request indicator to 1, if the UE:

a) initiates the mobility and periodic registration updating procedure upon request of the upper layers to establish an emergency PDU session;

[TS 22.101, subclause 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.4.4.3 Test description

11.4.4.3.1 Pre-test conditions

System Simulator:

– 2 NR Cells

– NR Cell 1 and NR Cell 11 as defined in TS 38.508-1 [4] Table 4.4.2-3.

– On all cells when active: System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport.

UE:

None.

Preamble:

– Cells power level configuration in accordance with TS 38.508-1 [4], Table 6.2.2.1-3:

– NR Cell 1 "Serving cell"

– NR Cell 11 "Non-Suitable "Off" cell"

– The UE is in test state 1N-A as defined in TS 38.508-1 [4], subclause 4.4A.2 on NR Cell 1

– During the initial registration:

– The list of tracking areas provided by the AMF (IE ‘TAI list’) contains only the TAI of NR Cell 1.

11.4.4.3.2 Test procedure sequence

Table 11.4.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures:

– NR Cell 11 as "Serving cell"

– NR Cell 1 as "Non-Suitable "Off" cell".

–

–

–

–

–

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

–

–

–

–

2

The UE transmits an RRCSetupRequest message.

–>

NR RRC: RRCSetupRequest

–

–

3

SS transmit an RRCSetup message.

<–

NR RRC: RRCSetup

–

–

4

The UE transmits an RRCSetupComplete message to confirm the successful completion of the connection establishment and a REGISTRATION REQUEST message indicating "mobility registration updating" is sent to update the registration of the actual tracking area.

–>

NR RRC: RRCSetupComplete

5GMM: REGISTRATION REQUEST

–

–

5

SS sends a REGISTRATION REJECT message containing 5GMM cause value = #22 (Congestion).

<–

NR RRC: DLInformationTransfer

5GMM: REGISTRATION REJECT

–

–

6

The SS transmits an RRCRelease message.

<–

NR RRC: RRCRelease

–

–

7

Make the UE attempt an IMS emergency call dialling an emergency number e.g. 112 or 911). (NOTE 1)

–

–

–

–

8

Check: Does the UE perform steps 1-3 from the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5

–

–

1

P

8AA

The SS transmits a SecurityModeCommand message.

<–

NR RRC: SecurityModeCommand

–

–

8AB

The UE transmits a SecurityModeComplete message.

–>

NR RRC: SecurityModeComplete

–

–

8AC

The UE performs steps 4-5 from the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5?

–

–

–

–

8A

Check: Does the UE transmit an UL NAS TRANSPORT message with ‘Request type’ set to ‘initial emergency request’, and, a PDU SESSION ESTABLISHMENT REQUEST for establishing an emergency PDU?

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT REQUEST

1

P

9-9D

Steps 9-13 from Generic Test Procedure for IMS Emergency call establishment with IMS Emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11, including the parallel behaviour specified in table 4.9.11.2.2-2 are performed.

–

–

–

–

10

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

11

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

–

EXCEPTION: Steps 12-13 below are repeated pc_noOf_PDUs times. The SS releases all active PDUs due to insufficient resources.

–

–

–

–

12

The SS sends a PDU SESSION RELEASE COMMAND including 5GSM cause #26 “insufficient resources", and, Back-off timer value IE, which provides the value of the T3396, set to a value which is neither zero nor a value which indicates that the timer is deactivated.

<–

NR RRC: DLInformationTransfer

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION RELEASE COMMAND

–

–

13

The UE transmits a PDU SESSION RELEASE COMPLETE.

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION RELEASE COMPLETE

–

–

14

The SS releases the RRC connection.

–

NR RRC: RRCRelease

–

–

15

Make the UE attempt an IMS emergency call dialling an emergency number e.g. 112 or 911). (NOTE 1)

–

–

–

–

16A-16E

Check: Does the UE perform steps 1-5 of Generic Test Procedure for IMS Emergency call establishment with IMS Emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

2

P

16F

The SS transmits a SERVICE ACCEPT message.

<–

NR RRC: DLInformationTransfer

5GMM: SERVICE ACCEPT

–

–

16G-16L

Check: Does the UE perform steps 8-13 of Generic Test Procedure for IMS Emergency call establishment with IMS Emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

2

P

17

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

18

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

11.4.4.3.3 Specific message contents

Table 11.4.4.3.3-0: REGISTRATION REQUEST (step 4, Table 11.4.4.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6, Condition MOBILITY MOBILITY.

Table 11.4.4.3.3-1: REGISTRATION REJECT (step 5, Table 11.4.4.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-9

Information Element

Value/remark

Comment

Condition

5GMM cause

‘00010110’B

#22 (Congestion)

T3346 value

‘00100011’B

3 minutes

Table 11.4.4.3.3-2: REGISTRATION REQUEST (step 8, Table 11.4.4.3.2-1; step 3, TS 38.508-1 [4] Table 4.9.5.2.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6, Condition.

Table 11.4.4.3.3-3: UL NAS TRANSPORT (step 8A, Table 11.4.4.3.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 11.4.4.3.3-4: PDU SESSION ESTABLISHMENT REQUEST (step 8A, Table 11.4.4.3.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 11.4.4.3.3-5: PDU SESSION RELEASE COMMAND (step 12)

Derivation Path: TS 38.508-1 [4] Table 4.7.2-14

Information Element

Value/remark

Comment

Condition

PDU session ID

An ID of an existing PDU session

5GSM cause

‘0001 1010’B

insufficient resources

Back-off timer value

‘1010 0101’B

5 minutes

Table 11.4.4.3.3-6: RRCReconfiguration (step 16H, Table 11.4.4.3.2-1; step 9, TS 38.508-1 [4] Table 4.9.11.2.2-1)

Derivation Path: TS 38.508-1 [4] Table 4.8.1-1B: RRCReconfiguration-SRB2-DRB(1,0)

11.4.5 5GMM-REGISTERED.LIMITED-SERVICE / 5GMM-IDLE / Emergency call establishment and release / Handling of 5GS forbidden tracking areas for roaming

11.4.5.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED.LIMITED-SERVICE state and 5GMM-IDLE mode }

ensure that {

when { UE is requested to make an Emergency call }

then { UE establishes the Emergency call }

}

(2)

with { UE in 5GMM-REGISTERED.LIMITED-SERVICE state and 5GMM-IDLE mode having established an Emergency call }

ensure that {

when { UE is requested to release the Emergency call }

then { UE releases the Emergency call, and, the UE considers the current cell as belonging to 5GS forbidden tracking areas for roaming }

}

11.4.5.2 Conformance requirement

References: The conformance requirements covered in the present TC are specified in: TS 24.501 [22], subclause 5.5.1.3.5, TS 23.122 [38], subclause 3.4.2. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, subclause 5.5.1.3.5]

#15 (No suitable cells in tracking area).

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2). The UE shall reset the registration attempt counter and shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304 [28].

The UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and shall remove the current TAI from the stored TAI list, if present.

If the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301 [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value.

[TS 23.122, subclause 3.4.2]

The MS is not allowed to request 5GS services except emergency services when camped on a cell of a TA of which belongs to the list of "5GS forbidden tracking areas for regional provision of service".

11.4.5.3 Test description

11.4.5.3.1 Pre-test conditions

System Simulator:

– 2 NR Cells

– NR Cell 1 and NR Cell 11 as defined in TS 38.508-1 [4], Table 4.4.2-3.

– On all cells when active: System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport.

UE:

None.

Preamble:

– Cell configuration " in accordance with TS 38.508-1 [4], Table 4.4.2-3:

– NR Cell 1 "Serving cell"

– NR Cell 11 "Non-Suitable "Off" cell"

– The UE is in test state 1N-A as defined in TS 38.508-1 [4], subclause 4.4A.2 on NR Cell 1

– During the initial registration:

– In the list of tracking areas provided by the AMF (IE ‘TAI list’) contains only the TAI of NR Cell 1.

11.4.5.3.2 Test procedure sequence

Table 11.4.5.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures:

– NR Cell 11 as "Serving cell"

– NR Cell 1 as "Non-Suitable "Off" cell".

–

–

–

–

–

EXCEPTION: The following messages are to be observed on NR Cell 11 unless explicitly stated otherwise.

–

–

–

–

2

The UE transmits an RRCSetupRequest message.

–>

NR RRC: RRCSetupRequest

–

–

3

SS transmit an RRCSetup message.

<–

NR RRC: RRCSetup

–

–

4

The UE transmits an RRCSetupComplete message to confirm the successful completion of the connection establishment and a REGISTRATION REQUEST message indicating "mobility registration updating" is sent to update the registration of the actual tracking area.

–>

NR RRC: RRCSetupComplete

5GMM: REGISTRATION REQUEST

–

–

5

SS sends a REGISTRATION REJECT message containing 5GMM cause value = #15 (No suitable cells in tracking area).

<–

NR RRC: DLInformationTransfer

5GMM: REGISTRATION REJECT

–

–

6

The SS transmits an RRCRelease message.

<–

NR RRC: RRCRelease

–

–

7

Make the UE attempt an IMS emergency call dialling an emergency number e.g. 112 or 911). (NOTE 1)

–

–

–

–

8

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment without IMS Emergency registration as specified in TS 38.508-1 [4], subclause 4.9.12?

–

–

1

P

9

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

10

Void

–

–

–

–

10A

the Generic test procedure for IMS MO Emergency call release with ‘release emergency PDU session’ as specified in TS 38.508-1 [4], subclause 4.9.12A take place.

–

–

–

–

10B-12b1

Void

–

–

–

–

12A

The SS transmits an RRCRelease message.

<–

NR RRC: RRCRelease

–

–

12B

Make the UE attempt an IMS non-emergency call. (NOTE 2)

–

–

–

–

12C

Check: Does the UE transmit an RRCSetupRequest message for initial registration procedure on NR Cell 11 within the next 10 seconds?

–>

NR RRC: RRCSetupRequest

2

F

13

The SS configures:

– NR Cell 1 as "Suitable neighbour intra-frequency cell"

– NR Cell 11 as "Non-suitable cell".

–

–

–

–

14

Check: Does the UE transmit an RRCSetupRequest message on NR Cell 1

–

–

2

P

15-16

Steps 3-4 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed.

–

–

–

–

–

EXCEPTION: Steps 17a1 to 17b3a1 describe behaviour that depends on events happening prior to their execution; the "lower case letter" identifies a step sequence that take place if a specific prior event takes place.

–

–

–

–

17a1-17a16a1

IF 5GS registration type is set as Initial Registration in step 16, THEN Steps 5 to 20a1 of the generic test procedure in TS 38.508-1 Table 4.5.2.2-2 are performed on NR Cell 1.

–

–

–

–

17b1-17b3a1

IF 5GS registration type is set as Mobility Registration in step 16, THEN Steps 4 to 6a1 of the generic test procedure in TS 38.508-1 Table 4.9.5.2.2-1 are performed on NR Cell 1.

–

–

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

NOTE 2: This could be done by e.g. MMI or AT command.

Table 11.4.5.3.2-2: Void

Table 11.4.5.3.2-3: Void

11.4.5.3.3 Specific message contents

Table 11.4.5.3.3-1: REGISTRATION REJECT (step 5, Table 11.4.5.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.7.1-9

Information Element

Value/remark

Comment

Condition

5GMM cause

‘00001111’B

#15 (No suitable cells in tracking area).

11.4.6 5GMM-REGISTERED.NON-ALLOWED-SERVICE / Emergency call establishment and release / Handling of non-allowed tracking areas

11.4.6.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED.NON-ALLOWED-SERVICE state and 5GMM-IDLE mode }

ensure that {

when { UE is requested to make an Emergency call }

then { UE establishes the Emergency call }

}

(2)

with { UE in 5GMM-REGISTERED.NON-ALLOWED-SERVICE state and 5GMM-CONNECTED mode having established an Emergency call }

ensure that {

when { UE is requested to release the Emergency call }

then { UE releases the Emergency call, and, the UE considers the current cell as belonging to non-allowed tracking areas }

}

11.4.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501 [22], subclause 5.3.5, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, subclause 5.3.5]

When the UE receives a Service area list IE with a non-allowed area indication during a registration procedure or a generic UE configuration update procedure, the UE shall delete the old list of "non-allowed tracking areas" and store the tracking areas in the non-allowed area as the list of "non-allowed tracking areas". If the UE has a stored list of "allowed tracking areas", the UE shall delete that list.

…

If the UE is successfully registered to a PLMN and has a stored list of "non-allowed tracking areas":

…

b) while camped on a cell whose TAI is in the list of "non-allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and:

1) if the UE is in 5GMM-IDLE mode over 3GPP access, the UE:

…

ii) shall not initiate a service request procedure except for emergency services, high priority access, responding to paging or notification or indicating a change of 3GPP PS data off UE status; and

[TS 22.101, subclause 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.4.6.3 Test description

11.4.6.3.1 Pre-test conditions

System Simulator:

– 2 NR Cells

– NR Cell 1 and NR Cell 11 as defined in TS 38.508-1 [4] Table 4.4.2-3.

– Maximum of 1 cell is active at any point of time.

– On all cells when active: System information combination NR-2 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport.

UE:

None.

Preamble:

– Cells power level configuration in accordance with TS 38.508-1 [4], Table 6.2.2.1-3:

– NR Cell 1 "Serving cell"

– NR Cell 11 "Non-Suitable "Off" cell"

– The UE is in test state 1N-A as defined in TS 38.508-1 [4], subclause 4.4A.2 on NR Cell 1

– During the initial registration:

– The list of tracking areas provided by the AMF (IE ‘TAI list’) contains only the TAI of NR Cell 1 whereas the TAI of NR Cell 11 is indicated in the Service area list IE with non-allowed areas as specified in Table 11.4.6.3.3-1.

11.4.6.3.2 Test procedure sequence

Table 11.4.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures:

– NR Cell 11 as "Serving cell"

– NR Cell 1 as "Non-Suitable "Off" cell"

–

–

–

–

–

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

–

–

–

–

2

The UE performs a registration for mobility procedure and the RRC connection is released according to generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1, which indicates that the UE is camped on NR Cell 11.

–

–

–

–

3

Make the UE attempt an IMS emergency call dialling an emergency number e.g. 112 or 911. (NOTE 1)

–

–

–

–

4

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS Emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

1

P

5

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

6

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

7

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

8

Make the UE attempt an IMS none-emergency call. (NOTE 1)

9

Check: Does the UE transmit in the next 10 sec an RRCSetupRequest message?

–>

NR RRC: RRCSetupRequest

2

F

NOTE 1: This could be done by e.g. MMI or AT command.

11.4.6.3.3 Specific message contents

Table 11.4.6.3.3-1: REGISTRATION ACCEPT (Preamble, step 2)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7.

Information Element

Value/remark

Comment

Condition

Service area list

Allowed type (octet 1)

‘1’B

TAIs in the list are in the non-allowed area

Type of list (octet 1)

’00’B

list of TACs belonging to one PLMN, with non-consecutive TAC values

Number of elements (octet 1)

‘00000’B

1 element

MCC

As defined for NR Cell 11 in TS 38.508-1 [4], Table 4.4.2-3.

MNC

As defined for NR Cell 11 in TS 38.508-1 [4], Table 4.4.2-3.

TAC 1

As defined for NR Cell 11 in TS 38.508-1 [4], Table 4.4.2-3.

11.4.7 Handling of Local and Extended emergency numbers / Mobility

11.4.7.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, UE receives a Local emergency numbers list in the REGISTRATION ACCEPT message, provided in the Emergency number list IE }

ensure that {

when { UE is requested to make an outgoing call using any of the emergency numbers received in the Local emergency numbers list }

then { UE establishes an IMS Emergency call }

}

(2)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, UE receives an Extended local emergency numbers list in the REGISTRATION ACCEPT message, provided in the Extended emergency number list IE }

ensure that {

when { UE is requested to make an outgoing call using any of the emergency numbers received in the Extended local emergency numbers list }

then { UE establishes an IMS Emergency call }

}

(3)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored a Local emergency numbers list and an Extended local emergency numbers list }

ensure that {

when { UE receives a new Local emergency numbers list in the REGISTRATION ACCEPT message, provided in the Emergency number list IE }

then { UE replaces the previously stored Local emergency numbers list }

}

(4)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored a Local emergency numbers list and an Extended local emergency numbers list }

ensure that {

when { UE receives a new Extended local emergency numbers list, in the REGISTRATION ACCEPT message, provided in the Extended emergency number list IE }

then { UE replaces the previously stored Extended local emergency numbers list }

}

(5)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored a Local emergency numbers list }

ensure that {

when { UE moves within the same PLMN from which the currently stored Local emergency numbers list provided in an Emergency number list IE were received, and, no Emergency number list IE is contained in the REGISTRATION ACCEPT message received during a Mobility and periodic update procedure }

then { UE keeps the stored Local emergency numbers list in the user equipment }

}

(6)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored an Extended local emergency numbers list }

ensure that {

when { UE moves within the same PLMN from which the currently stored Extended local Emergency Numbers List provided in an Extended emergency number list IE were received, and, no Extended emergency number list IE is contained in the REGISTRATION ACCEPT message received during a Mobility and periodic update procedure }

then { UE keeps the stored Extended local Emergency Numbers List in the user equipment }

}

(7)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored a Local emergency numbers list}

ensure that {

when { UE moves to a new PLMN in the same country as the PLMN from which the currently stored Local emergency numbers list provided in an Emergency number list IE were received, and, no Emergency number list IE is contained in the REGISTRATION ACCEPT message received in the new PLMN }

then { UE keeps the stored Local emergency numbers list in the user equipment }

}

(8)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored an Extended local emergency numbers list }

ensure that {

when { UE moves to a new PLMN in the same country as the PLMN from which the currently stored Extended Emergency Numbers List provided in an Extended emergency number list IE were received, and the Extended Emergency Number List Validity (EENLV) field within the Extended emergency number list IE indicated "Extended local Emergency Numbers List is valid in the country of the PLMN from which this IE is received", and, no Extended emergency number list IE is contained in the REGISTRATION ACCEPT message received in the new PLMN }

then { UE keeps the stored Extended local Emergency Numbers List in the user equipment }

}

(9)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored a Local emergency numbers list and an Extended local emergency numbers list }

ensure that {

when { UE moves to a new PLMN in the same country as the PLMN from which the currently stored Extended Emergency Numbers List provided in an Extended emergency number list IE were received, and the Extended Emergency Number List Validity (EENLV) field within the Extended emergency number list IE indicated "Extended local Emergency Numbers List is valid only in the PLMN from which this IE is received", and, no Extended emergency number list IE is contained in the REGISTRATION ACCEPT message received in the new PLMN }

then { UE deletes the stored Extended local Emergency Numbers List, and, keeps the stored Local emergency numbers list in the user equipment }

}

(10)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored a Local emergency numbers list }

ensure that {

when { UE moves to a new PLMN in a different country as the PLMN from which the currently stored Local emergency numbers list provided in an Emergency number list IE was received, and, no Emergency number list IE is contained in the REGISTRATION ACCEPT message received in the new PLMN }

then { UE deletes the stored Local emergency numbers list in the user equipment }

}

(11)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored an Extended local emergency numbers list }

ensure that {

when { UE moves to a new PLMN in a different country as the PLMN from which the currently stored Extended Emergency Numbers List provided in an Extended emergency number list IE were, and, no Extended emergency number list IE is contained in the REGISTRATION ACCEPT message received in the new PLMN }

then { UE deletes the stored Extended emergency numbers list in the user equipment }

}

11.4.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [12], subclause 5.3.3.3, TS 24.501 [22], subclause 5.3.12, TS 24.301 [21], subclause 5.3.7, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331, subclause 5.3.3.3]

The UE shall set the contents of RRCSetupRequest message as follows:

…

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCSetupRequest message to lower layers for transmission.

[TS 24.501, subclause 5.3.12]

The network may send a Local emergency numbers list or an Extended local emergency numbers list or both, in the REGISTRATION ACCEPT message, by including the Emergency number list IE and the Extended emergency number list IE, respectively. The Local emergency numbers list can be updated as described in 3GPP TS 24.301 [15], subclause 5.3.7.

The user equipment shall store the Local emergency numbers list and the Extended local emergency numbers list, as provided by the network. The Local emergency numbers list stored in the user equipment shall be replaced on each receipt of the Emergency number list IE. The Extended local emergency numbers list stored in the user equipment shall be replaced on each receipt of the Extended emergency number list IE. The received Local emergency numbers list or the received Extended local emergency numbers list or both shall be provided to the upper layers.

…

The emergency number(s) received in the Emergency number list IE are valid only in networks in the same country as the PLMN from which this IE is received. If no Emergency number list IE is contained in the REGISTRATION 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 in a country different from that of the PLMN that sent the list.

The emergency number(s) received in the Extended emergency number list IE are valid only in:

– networks in the same country as the PLMN from which this IE is received, if the Extended Emergency Number List Validity (EENLV) field within the Extended emergency number list IE indicates "Extended local Emergency Numbers List is valid in the country of the PLMN from which this IE is received"; and

– the PLMN from which this IE is received, if the EENLV field within the Extended emergency number list IE indicates "Extended local Emergency Numbers List is valid only in the PLMN from which this IE is received".

If no Extended local Emergency Numbers List is contained in the REGISTRATION ACCEPT message, and the registered PLMN has not changed, then the stored Extended local Emergency Numbers List in the user equipment shall be kept. If no Extended local Emergency Numbers List is contained in the REGISTRATION ACCEPT message, but the registered PLMN has changed, then:

– if the last received indication in the EENLV field within the Extended emergency number list IE indicates "Extended local Emergency Numbers List is valid only in the PLMN from which this IE is received", the stored Extended local Emergency Numbers List in the user equipment shall be deleted; and

– if the last received indication in the EENLV field within the Extended emergency number list IE indicates "Extended local Emergency Numbers List is valid in the country of the PLMN from which this IE is received" the list shall be kept except if the user equipment has successfully registered to a PLMN in a country different from that of the PLMN that sent the stored list.

NOTE: To prevent the misrouting of emergency calls, all operators within a country need to follow the regulation or agree on the setting of the Extended emergency number list IE in accordance to national agreement – either to indicate validity within a country or to indicate validity only within the PLMN.

The Local emergency numbers list and the Extended local emergency numbers list shall be deleted at switch off or removal of the USIM. The user equipment shall be able to store up to ten entries in the Local emergency numbers list and up to twenty entries in the Extended local emergency numbers list, received from the network.

For the use of the Local emergency numbers list and the Extended local emergency numbers list by the UE see 3GPP TS 24.301 [15], subclause 5.3.7.

[TS 24.301, subclause 5.3.7]

The Local Emergency Numbers List and the Extended local Emergency Numbers list contain additional Local emergency numbers used by the serving network. These lists can be downloaded by the network to the UE at successful registration and subsequent registration updates. There is only one Local Emergency Numbers List and only one Extended local Emergency Numbers list in the UE. The Local Emergency Numbers List can be updated with EMM procedures if the UE is in S1 mode, with GMM and MM procedures if the UE is in A/Gb or Iu mode, and with 5GMM procedures, as specified in 3GPP TS 24.501 [54], if UE is in N1 mode. The Extended local Emergency Numbers List can be updated with EMM procedures if the UE is in S1 mode and with 5GMM procedures, as specified in 3GPP TS 24.501 [54], if UE is in N1 mode.

The UE shall use the stored Local Emergency Numbers List and the stored Extended 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.

If the UE determines that the number dialled is an emergency number, the procedures specified in 3GPP TS 23.167 [45] and 3GPP TS 24.229 [13D] are utilised to select a domain for the emergency session attempt.

If the domain selected for the emergency session attempt is the PS domain, then the UE shall perform the session establishment procedures specified in 3GPP TS 24.229 [13D] to initiate an emergency session.

[TS 22.101, subclause 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.4.7.3 Test description

11.4.7.3.1 Pre-test conditions

System Simulator:

– 4 NR Cells

– NR Cell 1, NR Cell 3, NR Cell 11, NR Cell 12 as defined in TS 38.508-1 [4], Table 4.4.2-3, with the exception that cells’ PLMNs are defined in Table 11.4.7.3.1-1 below.

Table 11.4.7.3.1-1: PLMN identifiers

NR Cell

PLMN name

1

PLMN1

3

PLMN15

11

PLMN1

12

PLMN2

NOTE 1: PLMN1 is stored in EFIMSI on the test USIM card.

NOTE 2: PLMN1 and PLMN15 are in the same country; PLMN2 is in a different country.

– System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport.

NOTE: No more than 1 cell is active at any time throughout the test.

UE:

– The UE is equipped with a test USIM with USIM Configuration 20 as defined in TS 38.508-1 [4] Table 6.4.1-20 (USIM contains two Emergency Numbers: 144, 117).

Preamble:

– Cells signal level in accordance with TS 38.508-1 [4], Table 6.2.2.1-3:

– NR Cell 12 "Serving cell"

– NR Cell 1 "Non-Suitable "Off" cell"

– NR Cell 11 "Non-Suitable "Off" cell"

– NR Cell 3 "Non-Suitable "Off" cell"

– The UE is in test state 1N-A as defined in TS 38.508-1 [4], subclause 4.4A.2 on NR Cell 12.

– During the initial registration:

– Local emergency number(s) and Extended local emergency number(s) are provided by the Network as specified in Table 11.4.7.3.3-1.

11.4.7.3.2 Test procedure sequence

Table 11.4.7.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

–

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

–

–

–

–

1

Make the UE attempt an IMS call dialling number 120. (NOTE 1)

The number is expected to be stored in the Local emergency number list being received in the REGISTRATION ACCEPT message in the Preamble.

–

–

–

–

2

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

1

–

3

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

4

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

5

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

6

Make the UE attempt an IMS call dialling number 10. (NOTE 1)

The number is expected to be stored in the Extended local emergency number list being received in the REGISTRATION ACCEPT message in the Preamble.

–

–

–

–

7

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

2

–

8

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

9

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

10

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

–

The SS configures:

– NR Cell 1 as "Serving cell"

– NR Cell 12 as "Non-Suitable "Off" cell"

– NR Cell 11 as "Non-Suitable "Off" cell"

– NR Cell 3 as "Non-Suitable "Off" cell"

–

–

–

–

–

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

–

–

–

–

11

The UE performs the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5.

During the procedure the Network provides new Local emergency number list and Extended local emergency number list (EENLV=Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received) in the REGISTRATION ACCEPT message.

–

–

–

–

12

Make the UE attempt an IMS call dialling number 1001. (NOTE 1)

The number is expected to be stored in the Local emergency number list being received in the REGISTRATION ACCEPT message in step 11.

–

–

–

–

13

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

3

–

14

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

15

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

16

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

17

Make the UE attempt an IMS call dialling number 120. (NOTE 1)

The number was initially stored in the Local emergency number list being received in the REGISTRATION ACCEPT message in the Preamble but is expected to have been removed from the list when a new list was received in the REGISTRATION ACCEPT message in step 11.

–

–

–

–

18

Check: Does the UE performs Generic Test Procedure for IMS MO speech call establishment as specified in TS 38.508-1 [4], subclause 4.9.15?

–

–

3

–

19

Make the UE release the call. (NOTE 1)

–

–

–

–

20

The Generic test procedure for IMS MO call release as specified in TS 38.508-1 [4], subclause 4.9.17 takes place.

–

–

–

–

21

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

22

Make the UE attempt an IMS call dialling number 12345. (NOTE 1)

The number is expected to be stored in the Extended local emergency number list being received in the REGISTRATION ACCEPT message in step 11.

–

–

–

–

23

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

4

–

24

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

25

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

26

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

27

Make the UE attempt an IMS call dialling number 10. (NOTE 1)

The number was initially stored in the Extended local emergency number list being received in the REGISTRATION ACCEPT message in the Preamble but is expected to have been removed from the list when a new list was received in the REGISTRATION ACCEPT message in step 11.

–

–

–

–

28

Check: Does the UE performs Generic Test Procedure for IMS MO speech call establishment as specified in TS 38.508-1 [4], subclause 4.9.15?

–

–

4

–

29

Make the UE release the call. (NOTE 1)

–

–

–

–

30

The Generic test procedure for IMS MO call release as specified in TS 38.508-1 [4], subclause 4.9.17 takes place.

–

–

–

–

31

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

–

The SS configures:

– NR Cell 11 as "Serving cell"

– NR Cell 1 as "Non-Suitable "Off" cell"

– NR Cell 12 as "Non-Suitable "Off" cell"

– NR Cell 3 as "Non-Suitable "Off" cell"

–

–

–

–

–

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

–

–

–

–

32

The UE performs the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5.

During the procedure the Network does not send new Local emergency number list and Extended local emergency number list in the REGISTRATION ACCEPT message.

–

–

–

–

33

Make the UE attempt an IMS call dialling number 1001. (NOTE 1)

The number is expected to be stored in the Local emergency number list being received in the REGISTRATION ACCEPT message in step 11.

–

–

–

–

34

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

5

–

35

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

36

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

37

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

38

Make the UE attempt an IMS call dialling number 12345. (NOTE 1)

The number is expected to be stored in the Extended local emergency number list being received in the REGISTRATION ACCEPT message in step 11.

–

–

–

–

39

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

6

–

40

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

41

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

42

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

–

The SS configures:

– NR Cell 3 as "Serving cell"

– NR Cell 1 as "Non-Suitable "Off" cell"

– NR Cell 11 as "Non-Suitable "Off" cell"

– NR Cell 12 as "Non-Suitable "Off" cell"

–

–

–

–

–

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

–

–

–

–

43

The UE performs the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5.

During the procedure the Network does not send new Local emergency number list and Extended local emergency number list in the REGISTRATION ACCEPT message.

–

–

–

–

44

Make the UE attempt an IMS call dialling number 1001. (NOTE 1)

The number is expected to be stored in the Local emergency number list being received in the REGISTRATION ACCEPT message in step 11.

–

–

–

–

45

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

7

–

46

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

47

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

48

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

49

Make the UE attempt an IMS call dialling number 12345. (NOTE 1)

The number is expected to be stored in the Extended local emergency number list being received in the REGISTRATION ACCEPT message in step 11.

–

–

–

–

50

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

8

–

51

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

52

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

53

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

–

The SS configures:

– NR Cell 12 as "Serving cell"

– NR Cell 1 as "Non-Suitable "Off" cell"

– NR Cell 11 as "Non-Suitable "Off" cell"

– NR Cell 3 as "Non-Suitable "Off" cell"

–

–

–

–

–

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

–

–

–

–

54

The UE performs the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5.

During the procedure the Network does not send new Local emergency number list and Extended local emergency number list in the REGISTRATION ACCEPT message.

–

–

–

–

55

Make the UE attempt an IMS call dialling number 1001. (NOTE 1)

The number was initially stored in the Local emergency number list being received in the REGISTRATION ACCEPT message in step 11 but is expected to have been removed from the list when no new list was received in the REGISTRATION ACCEPT message in step 54.

–

–

–

–

56

Check: Does the UE performs Generic Test Procedure for IMS MO speech call establishment as specified in TS 38.508-1 [4], subclause 4.9.15?

–

–

10

–

57

Make the UE release the call. (NOTE 1)

–

–

–

–

58

The Generic test procedure for IMS MO call release as specified in TS 38.508-1 [4], subclause 4.9.17 takes place.

–

–

–

–

59

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

60

Make the UE attempt an IMS call dialling number 12345. (NOTE 1)

The number was initially stored in the Extended local emergency number list being received in the REGISTRATION ACCEPT message in step 11 but is expected to have been removed from the list when no new list was received in the REGISTRATION ACCEPT message in step 54.

–

–

–

–

61

Check: Does the UE performs Generic Test Procedure for IMS MO speech call establishment as specified in TS 38.508-1 [4], subclause 4.9.15?

–

–

11

–

62

Make the UE release the call. (NOTE 1)

–

–

–

–

63

The Generic test procedure for IMS MO call release as specified in TS 38.508-1 [4], subclause 4.9.17 takes place.

–

–

–

–

64

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

–

The SS configures:

– NR Cell 1 as "Serving cell"

– NR Cell 12 as "Non-Suitable "Off" cell"

– NR Cell 11 as "Non-Suitable "Off" cell"

– NR Cell 3 as "Non-Suitable "Off" cell"

–

–

–

–

–

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

–

–

–

–

65

The UE performs the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5.

During the procedure the Network provides new Local emergency number list and Extended local emergency number list (EENLV=Extended Local Emergency Numbers List is valid in the PLMN from which this IE is received) in the REGISTRATION ACCEPT message.

–

–

–

–

–

The SS configures:

– NR Cell 3 as "Serving cell"

– NR Cell 1 as "Non-Suitable "Off" cell"

– NR Cell 11 as "Non-Suitable "Off" cell"

– NR Cell 12 as "Non-Suitable "Off" cell"

–

–

–

–

–

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

–

–

–

–

66

The UE performs the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5.

During the procedure the Network does not send new Local emergency number list and Extended local emergency number list in the REGISTRATION ACCEPT message.

–

–

–

–

67

Make the UE attempt an IMS call dialling number 12345. (NOTE 1)

The number was initially stored in the Extended local emergency number list being received in the REGISTRATION ACCEPT message in step 65 but is expected to have been removed from the list when no new list was received in the REGISTRATION ACCEPT message in step 66.

–

–

–

–

68

Check: Does the UE performs Generic Test Procedure for IMS MO speech call establishment as specified in TS 38.508-1 [4], subclause 4.9.15?

–

–

9

–

69

Make the UE release the call. (NOTE 1)

–

–

–

–

70

The Generic test procedure for IMS MO call release as specified in TS 38.508-1 [4], subclause 4.9.17 takes place.

–

–

–

–

71

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

72

Make the UE attempt an IMS call dialling number 1001. (NOTE 1)

The number was initially stored in the Local emergency number list being received in the REGISTRATION ACCEPT message in step 65 and is not expected to have been removed from the list when no new list was received in the REGISTRATION ACCEPT message in step 66.

–

–

–

–

73

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

9

–

74

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

75

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

76

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

11.4.7.3.3 Specific message contents

Table 11.4.7.3.3-1: REGISTRATION ACCEPT (Preamble)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7.

Information Element

Value/remark

Comment

Condition

Emergency number list

Emergency Number information

120

TS 24.008 [43], 10.5.3.13.

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

Extended emergency number list

EENLV

‘0’

Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received

Emergency Number information

10

TS 24.301 [21], 9.9.3.37A.

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

Table 11.4.7.3.3-2: REGISTRATION ACCEPT (step 11, Table 11.4.7.3.2-1; step 4, TS 38.508-1 [4], Table 4.9.5.2.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7.

Information Element

Value/remark

Comment

Condition

Emergency number list

Emergency Number information

1 number: 1001

TS 24.008 [43], 10.5.3.13.

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

Extended emergency number list

EENLV

‘0’

Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received

Emergency Number information

1 number: 12345

TS 24.301 [21], 9.9.3.37A.

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

Table 11.4.7.3.3-3: REGISTRATION ACCEPT (step 65, Table 11.4.7.3.2-1; step 4, TS 38.508-1 [4], Table 4.9.5.2.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7.

Information Element

Value/remark

Comment

Condition

Emergency number list

Emergency Number information

1 number: 1001

TS 24.008 [43], 10.5.3.13.

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

Extended emergency number list

EENLV

‘1’

Extended Local Emergency Numbers List is valid in the PLMN from which this IE is received

Emergency Number information

1 number: 12345

TS 24.301 [21], 9.9.3.37A.

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

11.4.8 Handling of Local and extended emergency numbers / Switch-off and maximum local numbers storage

11.4.8.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored a Local emergency numbers list }

ensure that {

when { UE is switched off or the USIM is removed }

then { UE deletes the stored Local emergency numbers list in the user equipment }

}

(2)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, having stored an Extended local emergency numbers list }

ensure that {

when { UE is switched off or the USIM is removed }

then { UE deletes the stored Extended local Emergency Numbers List in the user equipment }

}

(3)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, UE receives a Local emergency numbers list with 10 entries in the REGISTRATION ACCEPT message, provided in the Emergency number list IE and the UE has stored them in local emergency numbers list }

ensure that {

when { UE is requested to make an outgoing call using any of the emergency numbers received in the Local emergency numbers list }

then { UE establishes an IMS Emergency call }

}

(4)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode, UE receives an Extended local emergency numbers list with 20 entries, in the REGISTRATION ACCEPT message, provided in the Extended emergency number list IE and the UE has stored them in Extended local emergency numbers lists }

ensure that {

when { UE is requested to make an outgoing call using any of the emergency numbers received in the Extended local emergency numbers list }

then { UE establishes an IMS Emergency call }

}

11.4.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [12], subclause 5.3.3.3, TS 24.501 [22], subclause 5.3.12, TS 24.301 [21], subclause 5.3.7, TS 22.101 [42], subclause 10.1.1. The following represents a copy/paste extraction of the requirements relevant to the test purpose; any references within the copy/paste text should be understood within the scope of the core spec they have been copied from. Unless otherwise stated these are Rel-15 requirements.

[TS 38.331 [12], subclause 5.3.3.3]

The UE shall set the contents of RRCSetupRequest message as follows:

…

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCSetupRequest message to lower layers for transmission.

[TS 24.501 [22], subclause 5.3.12]

The network may send a Local emergency numbers list or an Extended local emergency numbers list or both, in the REGISTRATION ACCEPT message, by including the Emergency number list IE and the Extended emergency number list IE, respectively. The Local emergency numbers list can be updated as described in 3GPP TS 24.301 [15], subclause 5.3.7.

The user equipment shall store the Local emergency numbers list and the Extended local emergency numbers list, as provided by the network. The Local emergency numbers list stored in the user equipment shall be replaced on each receipt of the Emergency number list IE. The Extended local emergency numbers list stored in the user equipment shall be replaced on each receipt of the Extended emergency number list IE. The received Local emergency numbers list or the received Extended local emergency numbers list or both shall be provided to the upper layers.

…

The Local emergency numbers list and the Extended local emergency numbers list shall be deleted at switch off or removal of the USIM. The user equipment shall be able to store up to ten entries in the Local emergency numbers list and up to twenty entries in the Extended local emergency numbers list, received from the network.

For the use of the Local emergency numbers list and the Extended local emergency numbers list by the UE see 3GPP TS 24.301 [15], subclause 5.3.7.

[TS 24.301 [21], subclause 5.3.7]

The Local Emergency Numbers List and the Extended local Emergency Numbers list contain additional Local emergency numbers used by the serving network. These lists can be downloaded by the network to the UE at successful registration and subsequent registration updates. There is only one Local Emergency Numbers List and only one Extended local Emergency Numbers list in the UE. The Local Emergency Numbers List can be updated with EMM procedures if the UE is in S1 mode, with GMM and MM procedures if the UE is in A/Gb or Iu mode, and with 5GMM procedures, as specified in 3GPP TS 24.501 [54], if UE is in N1 mode. The Extended local Emergency Numbers List can be updated with EMM procedures if the UE is in S1 mode and with 5GMM procedures, as specified in 3GPP TS 24.501 [54], if UE is in N1 mode.

The UE shall use the stored Local Emergency Numbers List and the stored Extended 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.

If the UE determines that the number dialled is an emergency number, the procedures specified in 3GPP TS 23.167 [45] and 3GPP TS 24.229 [13D] are utilised to select a domain for the emergency session attempt.

If the domain selected for the emergency session attempt is the PS domain, then the UE shall perform the session establishment procedures specified in 3GPP TS 24.229 [13D] to initiate an emergency session.

[TS 22.101 [42], subclause 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.4.8.3 Test description

11.4.8.3.1 Pre-test conditions

System Simulator:

– 2 NR Cells

– NR Cell 1 and NR Cell 12 as defined in TS 38.508-1 [4], Table 4.4.2-3. System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport.

– No more than 1 cell is active at any time throughout the test.

UE:

– The UE is equipped with a test USIM with USIM Configuration 20 as defined in TS 38.508-1 [4], Table 6.4.1-20 (USIM contains two Emergency Numbers: 144, 117).

Preamble:

– Cells signal level in accordance with TS 38.508-1 [4], Table 6.2.2.1-3:

– NR Cell 1 "Serving cell"

– NR Cell 12 "Non-Suitable "Off" cell"

– The UE is in state SWITCHED_OFF as defined in TS 38.508-1 [4], subclause 4.5.5.

– During the initial registration on NR Cell 1:

– Local emergency number(s) and Extended local emergency number(s) are provided by the Network as specified in Table 11.4.8.3.3-1.

11.4.8.3.2 Test procedure sequence

Table 11.4.8.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

–

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

–

–

–

–

1

Power on the UE.

–

–

–

–

2

The Generic test procedure for NR RRC_IDLE described in TS 38.508-1 [4], Table 4.5.2.2-2 is performed. The UE performs registration and the RRC connection is released.

During the procedure the SS does not send new Local emergency number list and Extended local emergency number list in the REGISTRATION ACCEPT message.

–

–

–

–

3

Make the UE attempt an IMS call dialling number 120. (NOTE 1)

The number was initially stored in the Local emergency number list being received in the REGISTRATION ACCEPT message in the Preamble but is expected to have been removed from the list upon switch-off.

–

–

–

–

4

Check: Does the UE performs Generic Test Procedure for IMS MO speech call establishment as specified in TS 38.508-1 [4], subclause 4.9.15?

–

–

1

–

5

Make the UE release the call. (NOTE 1)

–

–

–

–

6

The Generic test procedure for IMS MO call release as specified in TS 38.508-1 [4], subclause 4.9.17 takes place.

–

–

–

–

7

SS releases the RRC connection.

<–

NR RRC: RRCRelease

–

–

8

Make the UE attempt an IMS call dialling number 10. (NOTE 1)

The number was initially stored in the Extended local emergency number list being received in the REGISTRATION ACCEPT message in the Preamble but is expected to have been removed from the list upon switch-off.

–

–

–

–

9

Check: Does the UE performs Generic Test Procedure for IMS MO speech call establishment as specified in TS 38.508-1 [4], subclause 4.9.15?

–

–

2

–

10

Make the UE release the call. (NOTE 1)

–

–

–

–

11

The Generic test procedure for IMS MO call release as specified in TS 38.508-1 [4], subclause 4.9.17 takes place.

–

–

–

–

12

SS releases the RRC connection.

<–

NR RRC: RRCRelease

–

–

–

The SS configures:

– NR Cell 12 as "Serving cell"

– NR Cell 1 as "Non-Suitable "Off" cell"

–

–

–

–

–

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

–

–

–

–

13

The UE performs the Registration procedure for mobility registration update as specified in TS 38.508-1 [4] subclause 4.9.5.

During the procedure the UE receives new Local emergency number list with 10 entries and Extended local emergency number list with 20 entries in the REGISTRATION ACCEPT message.

–

–

–

–

–

EXCEPTION: Steps 14-18 are repeated 10 times. Each iteration shall be started with different number being dialled. The following Local emergency numbers received in the REGISTRATION ACCEPT message in step 13 shall be used: 120 … 129.

–

–

–

–

14

Make the UE attempt an IMS call dialling one of the numbers specified in the EXCEPTION step above. (NOTE 1)

–

–

–

–

15

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

3

–

16

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

17

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

18

SS releases the RRC connection.

<–

NR RRC: RRCRelease

–

–

–

EXCEPTION: Steps 19-23 are repeated 20 times. Each iteration shall be started with different number being dialled. The following Extended local emergency numbers received in the REGISTRATION ACCEPT message in step 13 shall be used: 130 … 149.

–

–

–

–

19

Make the UE attempt an IMS call dialling one of the numbers specified in the EXCEPTION step above. (NOTE 1)

–

–

–

–

20

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11?

–

–

4

–

21

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

22

The Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A takes place.

–

–

–

–

23

SS releases the RRC connection.

<–

NR RRC: RRCRelease

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

11.4.8.3.3 Specific message contents

Table 11.4.8.3.3-1: REGISTRATION ACCEPT (Preamble)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7.

Information Element

Value/remark

Comment

Condition

Emergency number list

Emergency Number information

120

TS 24.008 [43], 10.5.3.13.

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

Extended emergency number list

EENLV

‘0’

Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received

Emergency Number information

10

TS 24.301 [21], 9.9.3.37A.

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

Table 11.4.8.3.3-2: REGISTRATION ACCEPT (step 13, Table 11.4.8.3.2-1; step 4, TS 38.508-1 [4], Table 4.9.5.2.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-7.

Information Element

Value/remark

Comment

Condition

Emergency number list

Emergency Number information

10 numbers: 120 … 129

TS 24.008 [43], 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 [42] clause 10.1.1 a)-c).

Extended emergency number list

EENLV

‘0’

Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received

Emergency Number information

20 numbers:

130 … 149

TS 24.301 [21], 9.9.3.37A.

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

11.4.9 5GMM-DEREGISTERED.LIMITED-SERVICE No suitable cells in tracking area / Emergency call establishment and release

11.4.9.1 Test Purpose (TP)

(1)

with { UE in 5GMM-DEREGISTERED.LIMITED-SERVICE state after receiving REGISTRATION REJECT message with 5GMM cause value #15 ‘No suitable cells in tracking area’ }

ensure that {

when { UE is requested to make an Emergency call }

then { UE establishes an RRC connection with the RRC establishmentCause set to "emergency", and, attempts an Initial registration for emergency services by sending a REGISTRATION REQUEST message with IE Service type set to "emergency services", and, accepts and applies security with NULL security and integrity algorithms, and, after successful completion of the registration for emergency services establishes an emergency PDU session by sending an UL NAS TRANSPORT message with Request type set to "initial emergency request" and a PDU SESSION ESTABLISHMENT REQUEST }

}

(2)

with { UE in 5GMM-DEREGISTERED.LIMITED-SERVICE state after receiving REGISTRATION REJECT message with 5GMM cause value #15 ‘No suitable cells in tracking area’ and having established an Emergency call }

ensure that {

when { UE is requested to release the Emergency call }

then { UE releases the Emergency call, and, the UE considers the current cell as belonging to 5GS forbidden tracking areas for roaming }

}

11.4.9.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331 [12], subclause 5.3.3.3, TS 23.501 [37], subclause 5.16.4.1, TS 23.122 [38], subclause 3.4.2, TS 24.501 [22], subclauses 5.5.1.2.5, 4.4.4.1, 5.1.3.2.1.3.3, 5.3.2, 5.4.2.3, 5.5.1.2.2, 6.4.1.2, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, subclause 5.5.1.2.5]

If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value.

…

The UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message.

…

#15 (No suitable cells in tracking area).

The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2). The UE shall reset the registration attempt counter and shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304 [28].

The UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and shall remove the current TAI from the stored TAI list, if present.

If the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301 [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value.

[TS 23.122, subclause 3.4.2]

The MS is not allowed to request 5GS services except emergency services when camped on a cell of a TA of which belongs to the list of "5GS forbidden tracking areas for regional provision of service".

[TS 36.331, subclause 5.3.3.3]

The UE shall set the contents of RRCSetupRequest message as follows:

…

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCSetupRequest message to lower layers for transmission.

[TS 23.501, subclause 5.16.4.1]

UEs that are in limited service state, as specified in TS 23.122 [17], or that camp normally on a cell but failed to register successfully to the network under conditions specified in TS 24.501 [47], initiate the Registration procedure by indicating that the registration is to receive Emergency Services, referred to as Emergency Registration, and a Follow-on request is included in the Registration Request to initiate PDU Session Establishment procedure with a Request Type indicating "Emergency Request". UEs that had registered for normal services and do not have emergency PDU Sessions established and that are subject to Mobility Restriction in the present area or RAT (e.g. because of restricted tracking area) shall initiate the UE Requested PDU Session Establishment procedure to receive Emergency Services, i.e. with a Request Type indicating "Emergency Request". Based on local regulation, the network supporting Emergency Services for UEs in limited service state provides Emergency Services to these UE, regardless whether the UE can be authenticated, has roaming or Mobility Restrictions or a valid subscription.

[TS 24.501, subclause 4.4.4.1]

The use of "null integrity protection algorithm" 5G-IA0 (see subclause 9.11.3.32) in the current 5G NAS security context is only allowed for an unauthenticated UE for which establishment of emergency services is allowed. For setting the security header type in outbound NAS messages, the UE and the AMF shall apply the same rules irrespective of whether the "null integrity protection algorithm" or any other integrity protection algorithm is indicated in the 5G NAS security context.

If the "null integrity protection algorithm"5G-IA0 has been selected as an integrity protection algorithm, the receiver shall regard the NAS messages with the security header indicating integrity protection as integrity protected.

[TS 24.501, subclause 5.1.3.2.1.3.3]

The substate 5GMM-DEREGISTERED.LIMITED-SERVICE is chosen in the UE, when it is known that a selected cell for 3GPP access or TA for non-3GPP access is unable to provide normal service (e.g. the selected cell over 3GPP access is in a forbidden PLMN or is in a forbidden tracking area or TA for non-3GPP access is forbidden).

[TS 24.501, subclause 5.3.2]

The UE provides the SUPI to the network in concealed form. The SUCI is a privacy preserving identifier containing the concealed SUPI. When the SUPI contains a network specific identifier, the SUCI shall take the form of an NAI as specified in 3GPP TS 23.003 [4].

A UE supporting N1 mode includes a SUCI:

a) in the REGISTRATION REQUEST message when the UE is attempting initial registration procedure and a valid 5G-GUTI is not available; or

…

The UE shall use the "null-scheme" as specified in 3GPP TS 33.501 [24] to generate the SUCI, if the following applies:

a) the UE performs a registration procedure for emergency services or initiates a de-registration procedure before the registration procedure for emergency services was completed successfully; and

[TS 24.501, subclause 5.4.2.3]

If the UE is registered for emergency services, performing initial registration for emergency services or establishing an emergency PDU session and the SECURITY MODE COMMAND message is received with ngKSI value "000" and 5G-IA0 and 5G-EA0 as selected 5G NAS security algorithms, the UE shall locally derive and take in use 5G NAS security context. The UE shall delete existing current 5G NAS security context.

The UE shall accept a SECURITY MODE COMMAND message indicating the "null integrity protection algorithm" 5G-EA0 as the selected 5G NAS integrity algorithm only if the message is received when the UE is registered for emergency services, performing initial registration for emergency services or establishing an emergency PDU session.

[TS 24.501, subclause 5.5.1.2.2]

The UE in state 5GMM-DEREGISTERED shall initiate the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF,

…

b) when the UE performs initial registration for emergency services;

…

If the UE initiates an initial registration for emergency services or needs to prolong the established NAS signalling connection after the completion of the initial registration procedure (e.g. due to uplink signalling pending), the UE shall set the Follow-on request indicator to 1.

[TS 24.501, subclause 6.4.1.2]

In order to initiate the UE-requested PDU session establishment procedure, the UE shall create a PDU SESSION ESTABLISHMENT REQUEST message.

NOTE 0: When IMS voice is available over either 3GPP access or non-3GPP access, the "voice centric" UE in 5GMM-REGISTERED state will receive a request from upper layers to establish the PDU session for IMS signalling, if the conditions for performing an initial registration with IMS indicated in 3GPP TS 24.229 [14] subclause U.3.1.2 are satisfied.

If the UE requests to establish a new PDU session, the UE shall allocate a PDU session ID which is not currently being used by another PDU session over either 3GPP access or non-3GPP access.

The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION ESTABLISHMENT REQUEST message to the allocated PTI value.

…

If the UE requests to establish a new emergency PDU session, the UE shall set the SSC mode IE of the PDU SESSION ESTABLISHMENT REQUEST message to "SSC mode 1".

…

The UE shall transport:

a) the PDU SESSION ESTABLISHMENT REQUEST message;

b) the PDU session ID of the PDU session being established, or being handed over or being transferred;

..

e) the request type which is set to:

…

3) "initial emergency request", if the UE requests to establish a new emergency PDU session; and

…

If the request type is set to "initial emergency request" or "existing emergency PDU session", neither DNN nor S-NSSAI is transported by the UE using the NAS transport procedure as specified in subclause 5.4.5.

[TS 22.101, subclause 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.

11.4.9.3 Test description

11.4.9.3.1 Pre-test conditions

System Simulator:

– 1 NR Cell

– NR Cell 1, as defined in TS 38.508-1 [4], Table 4.4.2-3.

– System information combination NR-1 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2. SIB1 indicates ims-EmergencySupport.

UE:

None.

Preamble:

– The UE is in test state 0N-B (Switched Off) as defined in TS 38.508-1 [4], subclause 4.4A.2.

11.4.9.3.2 Test procedure sequence

Table 11.4.9.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Switch the UE on.

–

–

–

–

2-4

Steps 2-4 of Table 4.5.2.2-2 NR RRC_IDLE in TS38.508-1 [4] take place (the UE initiates an initial registration procedure).

–

–

–

–

5

SS sends a REGISTRATION REJECT message containing 5GMM cause value = #15 (No suitable cells in tracking area).

<–

NR RRC: DLInformationTransfer

5GMM: REGISTRATION REJECT

–

–

6

The SS transmits an RRCRelease message.

<–

NR RRC: RRCRelease

–

–

7

Make the UE attempt an IMS emergency call dialling a number which is stored on the ME (e.g. 112 or 911). (NOTE 1)

–

–

–

–

8

Check: Does the UE performs Generic Test Procedure for IMS Emergency call establishment without IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.12?

–

–

1

P

9

Make the UE release the emergency call. (NOTE 1)

–

–

–

–

10

Void

–

–

–

–

10A-10C

Steps 1-3 of the Generic test procedure for IMS MO Emergency call release as specified in TS 38.508-1 [4], subclause 4.9.12A

take place.

–

–

–

–

11

Start Timer T1=5 seconds.

NOTE: This is an arbitrary value to wait for UE initiated detach.

–

–

–

–

–

EXCEPTION: In parallel to step 12 below, the steps specified in Tables 11.4.9.3.2-2, and 11.4.9.3.2-3 may take place

–

–

–

–

12

Timer T1=5 seconds expires

–

–

–

–

12a1-12b3

Void

–

–

–

–

13

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

13A

Make the UE attempt an IMS none-emergency call. (NOTE 2)

–

–

–

–

14

Check: Does the UE transmit an RRCSetupRequest message in the next 10 seconds?

NOTE: This is an arbitrary value to wait for catching not allowed UE behaviour.

–>

NR RRC: RRCSetupRequest

2

F

NOTE 1: This could be done by e.g. MMI or AT command.

NOTE 2: This could be done by e.g. MMI or AT command.

Table 11.4.9.3.2-2: Parallel Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a DEREGISTRATION REQUEST message with De-registration type IE set to "Normal de-registration".

–>

NR RRC: ULInformationTransfer

5GMM: DEREGISTRATION REQUEST

–

–

2

The SS transmits a DEREGISTRATION ACCEPT message.

<–

NR RRC: DLInformationTransfer

5GMM: DEREGISTRATION ACCEPT

–

–

Table 11.4.9.3.2-3: Parallel Behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmits a PDU SESSION RELEASE REQUEST message.

–>

NR RRC: ULInformationTransfer

PDU SESSION RELEASE REQUEST

–

–

2

The SS transmits a PDU SESSION RELEASE COMMAND message.

<–

NR RRC: DLInformationTransfer NR NAS: PDU SESSION RELEASE COMMAND

–

–

3

Check: Does the UE transmit a PDU SESSION RELEASE COMPLETE message?

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION RELEASE COMPLETE

–

–

11.4.9.3.3 Specific message contents

Table 11.4.9.3.3-1: REGISTRATION REJECT (step 5, Table 11.4.9.3.2-1)

Derivation path: TS 38.508-1 [4] table 4.7.1-9.

Information Element

Value/remark

Comment

Condition

5GMM cause

‘00001111’B

#15 (No suitable cells in tracking area).

Table 11.4.9.3.3-2: REGISTRATION REQUEST (step 8, Table 11.4.9.3.2-1; step 3, TS 38.508-1 [4], Table 4.9.12.2.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6, condition EMERGENCY.

Information Element

Value/remark

Comment

Condition

5GS mobile identity

SUCI

The UE shall use the "null-scheme" as specified in 3GPP TS 33.501 [20] to generate the SUCI

Table 11.4.9.3.3-3: DEREGISTRATION REQUEST (Step 12a1, Table 11.4.9.3.2-1)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-12, Condition NORMAL.

Table 11.4.9.3.3-4: Void

11.4.10 Void

11.4.10a 5GMM-REGISTERED.NORMAL-SERVICE / N26 interface not supported / N1 mode to S1 mode transfer of an existing emergency PDU session

11.4.10a.1 Test Purpose (TP)

(1)

with { UE in 5GMM-REGISTERED.NORMAL-SERVICE state and 5GMM-IDLE mode with Interworking without N26 interface supported, and, the UE has an emergency PDU session established }

ensure that {

when { UE performs a inter-system change from the N1 to S1 mode }

then { UE correctly transfers the existing emergency PDU session into an emergency PDN connection }

}

11.4.10a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501 [22], subclause 6.1.4.2, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, subclause 6.1.4.2]

When the network does not support N26 interface, the SMF does not provide the UE with the mapped EPS bearer context for a PDU session.

NOTE 1: Since the SMF does not provide the UE with the mapped EPS bearer context for a PDU session, the UE does not know whether interworking with EPS is supported for a PDU session before attempting to transfer the PDU session from N1 mode to S1 mode.

NOTE 2: It is up to UE implementation to decide which PDU session(s) to be attempted to transfer from N1 mode to S1 mode, e.g. based on UE policy or UE local configuration.

…

Upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE shall use the parameters from each PDU session which the UE intends to transfer to EPS to create the contents of a PDN CONNECTIVITY REQUEST message as follows:

a) if the PDU session is an emergency PDU session, the request type shall be set to "handover of emergency bearer services". Otherwise the request type shall be set to "handover";

b) the PDU session type of the PDU session shall be mapped to the PDN type of the default EPS bearer context as follows:

1) the PDN type shall be set to "non-IP" if the PDU session type is "Ethernet" or "Unstructured";

2) the PDN type shall be set to "IPv4" if the PDU session type is "IPv4";

3) the PDN type shall be set to "IPv6" if the PDU session type is "IPv6"; and

4) the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6";

c) the DNN of the PDU session shall be mapped to the APN of the default EPS bearer context; and

d) the PDU session ID parameter in the PCO IE shall be set to the PDU session identity of the PDU session.

…

After inter-system change from N1 mode to S1 mode, the UE shall associate the PDU session identity with the default EPS bearer context.

[TS 22.101, subclause 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.

11.4.10a.3 Test description

11.4.10a.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-6 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2.

– E-UTRA Cell 1 as defined in TS 36.508 [7] Table 4.4.2-2. System information combination 31 as defined in TS 36.508 [7], subclause 4.4.3.1.1.

UE:

None.

Preamble:

With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state 1N-A, RRC_IDLE Connectivity (NR), in accordance with the procedure described in TS 38.508-1 [4], subclause 4.5.2 (Table 4.5.2.2-2 and depending on UE implementation Table 4.5.2.2-4). Interworking without N26 interface supported in accordance with the definition specified in TS 38.508-1 [4], subclause 4.5.1.

11.4.10a.3.2 Test procedure sequence

Table 11.4.10a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt an IMS emergency call dialling an emergency number. (NOTE 1)

–

–

–

–

–

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

–

–

–

–

2

The UE performs Generic Test Procedure for IMS Emergency call establishment with IMS emergency registration as specified in TS 38.508-1 [4], subclause 4.9.11.

–

–

–

–

2A

Make the UE release the IMS emergency call. (NOTE 1)

–

–

–

–

2B

Generic Test Procedure for IMS MO call release in 5GC as defined in TS 38.508-1 [4], Table 4.9.17.2.2-1 takes place.

The dedicated voice bearer is released but the Emergency session is not.

–

–

–

–

3

SS releases the RRC connection

<–

NR RRC: RRCRelease

–

–

4

The SS configures:

– E-UTRA Cell 1 as "Serving cell"

– NR Cell 1 as "Non-suitable "off" cell".

–

–

–

–

–

The following messages are to be observed on E-UTRA Cell 1 unless explicitly stated otherwise.

–

–

–

–

5-10

Void

–

–

–

–

–

EXCEPTION: Steps 10AAa1 to 10AAb3 describe behaviour that depends on the UE implementation; the "lower case letter" identifies a step sequence that take place depending on the UE implementation.

–

–

–

–

10AAa1

If the UE tries to preserve the IP address of the PDN connection then check does the UE transmits an ATTACH REQUEST message?

–>

RRC: RRCConnectionSetupComplete NAS: ATTACH REQUEST

–

–

10AAb1

Else check: does the UE transmit a TRACKING AREA UPDATE REQUEST message?

–>

RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST

–

–

10AAb2

The SS transmits a TRACKING AREA UPDATE REJECT message to UE.

<–

RRC: DLInformationTransfer

NAS: TRACKING AREA UPDATE REQUEST REJECT

–

–

10AAb3

The UE transmits an ATTACH REQUEST message.

–>

RRC: ULInformationTransfer

NAS: ATTACH REQUEST

–

–

10AB-10AM

Steps 5 to 16 of the generic test procedure for UE registration (TS 36.508 [7] Table 4.5.2.3-1)

–

–

–

–

–

EXCEPTION: In parallel to step 10Aa1 below the steps described in table 11.4.10a.3.2-2 take place.

–

–

–

–

10Aa1

Step 8a1 from the test procedure for UE for Tracking area updating / Inter-system change from N1 mode to S1 mode in 5GMM/EMM-IDLE mode as specified in TS 38.508-1 [4], Table 4.9.7.2.2-1, takes place performing establishment of UE-requested PDN connection(s) with ExpectedNumberOfNewPDNConnections = pc_noOf_PDNsSameConnection.

NOTE: The pc_noOf_PDNsSameConnection covers the "normal" PDNs the UE will establish when it attaches to EPC. This does not include the PDN connection for Emergency services – this is handled separately and in parallel in Table 11.4.10a.3.2-2.

–

–

–

–

10Ab2a1-10Ab2a8

Void

–

–

–

–

11

Wait 3 sec.

–

–

–

–

12

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

<–

DEACTIVATE EPS BEARER CONTEXT REQUEST

–

–

13

The UE transmit a DEACTIVATE EPS BEARER CONTEXT ACCEPT.

–>

DEACTIVATE EPS BEARER CONTEXT ACCEPT

–

–

14

SS releases the RRC connection.

<–

RRC: RRCConnectionRelease

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

Table 11.4.10a.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE transmit a PDN CONNECTIVITY REQUEST message to request an additional PDN, with ‘Request type’ set to ‘handover of emergency bearer services’?

–>

PDN CONNECTIVITY REQUEST

1

P

24-

Steps 10-12 from the Generic Test Procedure for IMS Emergency call establishment in EUTRA: Normal Service as specified in TS 36.508 [7], Table 4.5A.4.3-1 take place with the exception that the parallel to Table 4.5A.4.3-1 step 11 behaviour does not take place.

The default bearer for the Emergency connection is established

–

–

–

–

–

EXCEPTION: Step 5a1 describes a step sequence depending on UE implementation.

–

–

–

–

5a1

IMS re-registration on E-UTRAN as specified in TS 34.229-1 [35] subclause C.46, takes place.

–

–

–

–

11.4.10a.3.3 Specific message contents

Table 11.4.10a.3.3-1: REGISTRATION ACCEPT (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7, condition EMERGENCY

Information Element

Value/remark

Comment

Condition

5GS network feature support

‘0100 1101 0000 0000’B

IMS voice over PS session supported over 3GPP access,

Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN.

Interworking without N26 interface supported (octet 3, bit 7)

All other features set to "not supported".

Interworking without N26 interface supported

Table 11.4.10a.3.3-2: PDN CONNECTIVITY REQUEST (step 1, Table 11.4.10a.3.2-2)

Derivation Path: TS 36.508 [7], Table 4.7.2-1.

Information Element

Value/remark

Comment

Condition

Request type

‘110”B

‘handover of emergency bearer services’

PDN type

The PDU session type of the emergency PDU session established prior to the N1 to S1 move

The PDU session established in step 2, Table 11.4.10a.3.2-1

Access point name

sos

Protocol configuration options

Only the values indicated below are checked

protocol identifier

length of the protocol identifier contents of the unit

protocol identifier contents

Additional parameters list

container identifier

001AH

(PDU session ID)

container identifier contents

The PDU session ID of the emergency PDU session established prior to the N1 to S1 move.

Table 11.4.10a.3.3-3: ATTACH ACCEPT (preamble, step 10AK; step 14, TS 36.508-1 [7], Table 4.5.2.3-1)

Derivation path: TS 36.508-1 [7] Table 4.7.2-1

Information Element

Value/remark

Comment

Condition

EPS network feature support

‘0000 0011 0100 1000’B

– IMS voice over PS session in S1 mode supported

– emergency bearer services in S1 mode supported

– ePCO supported

– Interworking without N26 interface supported

Table 11.4.10a.3.3-4: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (preamble, step 10AK; step 14, TS 36.508-1 [7], Table 4.5.2.3-1)

Derivation Path: TS 36.508-1 [7] Table 4.7.3-6

Information Element

Value/remark

Comment

Condition

Protocol configuration options

Container ID n+2

Not present

Session-AMBR are not present

Container ID n+3

Not present

QoS rules are not present

Container ID n+4

Not present

Qos flow descriptions are not present

11.4.11 5GMM-REGISTERED.NORMAL-SERVICE / N26 interface not supported / S1 mode to N1 mode transfer of an existing emergency PDN connection

11.4.11.1 Test Purpose (TP)

(1)

with { UE in EMM-REGISTERED and EMM-IDLE on an E-UTRA cell, and, the UE has an emergency PDN connection established }

ensure that {

when { UE performs a inter-system change from the S1 to N1 mode, to an NR Cell belonging to a NWK supporting Interworking without N26 interface }

then { UE correctly transfers the existing emergency PDN connection into an emergency PDU session }

}

11.4.11.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501 [22], subclause 6.1.4.2, TS 22.101 [42], subclause 10.1.1. Unless otherwise stated these are Rel-15 requirements.

[TS 24.501, subclause 6.1.4.2]

When the network does not support N26 interface, the SMF does not provide the UE with the mapped EPS bearer context for a PDU session.

NOTE 1: Since the SMF does not provide the UE with the mapped EPS bearer context for a PDU session, the UE does not know whether interworking with EPS is supported for a PDU session before attempting to transfer the PDU session from N1 mode to S1 mode.

NOTE 2: It is up to UE implementation to decide which PDU session(s) to be attempted to transfer from N1 mode to S1 mode, e.g. based on UE policy or UE local configuration.

…

Upon inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, the UE uses the parameters from the default EPS bearer context of each PDN connection which the UE intends to transfer to 5GS and for which the UE has allocated a PDU session identity to create a PDU SESSION ESTABLISHMENT REQUEST message as follows:

a) if the PDN connection is for emergency bearer services, the request type shall be set to "existing emergency PDU session". Otherwise the request type shall be set to "existing PDU session";

b) the PDN type of the default EPS bearer context shall be mapped to the PDU session type of the PDU session as follows:

…

2) if the PDN type is "IPv4" the PDU session type is set to "IPv4";

3) if the PDN type is "IPv6", the PDU session type is set to "IPv6"; and

4) the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6";

c) the APN of the default EPS bearer context shall be mapped to the DNN of the PDU session;

d) the PDU session ID shall be set to the PDU session identity included by the UE in the Protocol configuration options IE or Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message, or to the PDU session ID associated with the default EPS bearer context; and

e) the S-NSSAI of the PDU session shall be set to the S-NSSAI included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, if provided by the network, or the S-NSSAI associated with the default EPS bearer context, if available.

NOTE 5: If T3584 is running or deactivated for the S-NSSAI and optionally the DNN combination, the UE is allowed to initiate ESM procedures in EPS with or without APN corresponding to that DNN, and if the APN is congested in EPS, the MME can send a back-off timer for the APN to the UE as specified in 3GPP TS 24.301 [15].

The UE shall locally release the PDN connection(s) and EPS bearer(s) associated with the 3GPP access which have not been transferred to 5GS.

[TS 22.101, subclause 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.

11.4.11.3 Test description

11.4.11.3.1 Pre-test conditions

System Simulator:

– 2 cells

– E-UTRA Cell 1 as defined in TS 36.508 [7] Table 4.4.2-2. System information combination 31 as defined in TS 36.508 [7], subclause 4.4.3.1.1.

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-6 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2.

UE:

None.

Preamble:

– With NR Cell 1 "Serving cell" and E-UTRA Cell 1 "Non-suitable "Off" cell", the UE is brought to state 1N-A, RRC_IDLE Connectivity (NR), in accordance with the procedure described in TS 38.508-1 [4], subclause 4.5.2 (Table 4.5.2.2-2 and depending on UE implementation Table 4.5.2.2-4). 5G-GUTI and ngKSI are assigned and security context established. During the registration the NWK indicates Interworking without N26 interface supported in accordance with the definition specified in TS 38.508-1 [4], subclause 4.5.1.

– the UE is switched-off

– With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell", the UE is brought to state RRC_IDLE Connectivity (E-UTRA/EPC) in accordance with the procedure described in TS 38.508-1 [4], Table 4.5.2.2-1. 4G GUTI and eKSI are assigned and security context established

11.4.11.3.2 Test procedure sequence

Table 11.4.11.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt an IMS emergency call dialling an emergency number. (NOTE 1)

–

–

–

–

–

The following messages are to be observed on E-UTRA Cell 1 unless explicitly stated otherwise.

–

–

–

–

2-15

Steps 2-15, from the Generic Test Procedure for IMS Emergency call establishment in EUTRA: Normal Service as specified in TS 36.508-1 [7], subclause 4.5A.4 take place.

–

–

–

–

15A

Make the UE release the IMS emergency call. (NOTE 1)

–

–

–

–

15B

The Generic test procedure for MO release of IMS call – EPS as defined in TS 34.229-1 [35], subclause C.32, takes place.

–

–

–

–

15C

The Generic Test Procedure for EPS Bearer Deactivation TS 36.508-1 [7], subclause 4.5A.15, take place.

The SS deactivates the dedicated for IMS voice EPS bearer context of the Emergency PDN connection. The default bearer is kept i.e. the Emergency session is not released.

–

–

–

–

16

SS releases the RRC connection on E-UTRA.

<–

RRC: RRCConnectionRelease

–

–

17

The SS configures:

– NR Cell 1 as "Serving cell"

– E-UTRA Cell 1 as "Non-suitable "off" cell".

–

–

–

–

–

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

–

–

–

–

18-28

Steps 1-11 from the test procedure for UE for Tracking area updating / Inter-system change from S1 mode to N1 mode in 5GMM/EMM-IDLE mode as specified in TS 38.508-1 [4], Table 4.9.9, take place.

–

–

–

–

–

EXCEPTION: In parallel to step 29Aa1 below the steps described in table 11.4.11.3.2-2 take place.

–

–

–

–

29a1

Step 14a1 from the test procedure for UE for Tracking area updating / Inter-system change from S1 mode to N1 mode in 5GMM/EMM-IDLE mode as specified in TS 38.508-1 [4], Table 4.9.9.2.2-1, takes place performing establishment of UE-requested PDU session(s) with ExpectedNumberOfNewPDUSessions = pc_noOf_PDUsSameConnection

NOTE: The pc_noOf_PDUsSameConnection covers the "normal" PDUs the UE will establish when it attaches to 5GC. This does not include the PDU connection for Emergency services – this is handled separately and in parallel in Table 11.4.11.3.2-2..

–

–

–

–

29a2a1-29b3a9

Void

–

–

–

–

30

Wait 3 sec.

–

–

–

–

31

The SS transmits a RRCReconfiguration message and a PDU SESSION RELEASE COMMAND message to release the Emergency session.

<–

NR RRC: RRCReconfiguration

NR NAS: PDU SESSION RELEASE COMMAND

–

–

32

The UE transmits a RRCReconfigurationComplete

–

NR RRC: RRCReconfigurationComplete

–

–

33

The UE transmits a PDU SESSION RELEASE COMPLETE message?

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION RELEASE COMPLETE

–

–

34

SS releases the RRC connection.

<–

NR RRC: RRCRelease

–

–

NOTE 1: This could be done by e.g. MMI or AT command.

Table 11.4.11.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the UE transmit an UL NAS TRANSPORT message with ‘Request type’ set to "existing emergency PDU session", and, a PDU SESSION ESTABLISHMENT REQUEST?

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT REQUEST

1

P

2

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

<–

NR RRC: RRCReconfiguration

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION ESTABLISHMENT ACCEPT

–

–

–

EXCEPTION: Step 3a1 describes a step sequence depending on UE implementation.

–

–

–

–

3a1

IMS re-registration on NR as specified in TS 34.229-5 [41], annex A.12, takes place.

–

–

–

–

11.4.11.3.3 Specific message contents

Table 11.4.11.3.3-1: REGISTRATION ACCEPT (Preamble)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7, condition EMERGENCY

Information Element

Value/remark

Comment

Condition

5GS network feature support

‘0100 1101 0000 0000’B

IMS voice over PS session supported over 3GPP access,

Emergency services supported in NR connected to 5GCN and E-UTRA connected to 5GCN.

Interworking without N26 interface supported (octet 3, bit 7)

All other features set to "not supported".

Interworking without N26 interface supported

Table 11.4.11.3.3-2: PDU SESSION ESTABLISHMENT REQUEST (step 1, Table 11.4.11.3.2-2)

Derivation Path: TS 38.508-1 [4], Table 4.7.2-1.

Information Element

Value/remark

Comment

Condition

PDU session ID

Shall be set to the PDU session identity included by the UE in the Protocol configuration options IE or Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message, or to the PDU session ID associated with the default EPS bearer context

PTI

A value currently not used

SSC mode

‘001’B

SSC mode 1

Table 11.4.11.3.3-3: UL NAS TRANSPORT (step 1, Table 11.4.11.3.2-2)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-10, condition INITIAL_PDU_REQUEST.

Information Element

Value/remark

Comment

Condition

Request type

‘100’B

existing emergency PDU session

S-NSSAI

Not Present

DNN

Not Present

Table 11.4.11.3.3-4: ATTACH ACCEPT (preamble)

Derivation path: TS 36.508-1 [7] Table 4.7.2-1

Information Element

Value/remark

Comment

Condition

EPS network feature support

‘0000 0011 0100 1000’B

– IMS voice over PS session in S1 mode supported

– emergency bearer services in S1 mode supported

– ePCO supported

– Interworking without N26 interface supported

Table 11.4.11.3.3-5: ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 10; TS 36.508-1 [7], Table 4.5.2.3-1)

Derivation Path: TS 36.508-1 [7] Table 4.7.3-6

Information Element

Value/remark

Comment

Condition

Protocol configuration options

Container ID n+2

Not present

Session-AMBR are not present

Container ID n+3

Not present

QoS rules are not present

Container ID n+4

Not present

Qos flow descriptions are not present

Container ID n+5

Not present

S-NSSAI are not present

11.4.12 5GMM-REGISTERED.NORMAL-SERVICE / 5GMM-IDLE / Emergency call / Disabling N1 mode / Emergency call establishment over EPS / Success

11.4.12.1 Test Purpose (TP)

(1)

with { UE supporting both S1 mode and N1 mode and operating in single-registration mode, and, the Network has indicated "interworking without N26 interface not supported", and, the Network has indicated "Emergency service Fallback not supported" regardless whether the UE supports emergency service fallback or not, and, the UE is in NR RRC_IDLE state }

ensure that {

when { User initiates an Emergency call and the UE completes Access control checking in 5GMM-IDLE mode }

then { UE selects the E-UTRA cell, and, requests the establishment of an Emergency call by transmitting an RRCConnectionRequest message with establishmentCause set to ’emergency’ }

}

(2)

with { UE establishes RRC connection in E-UTRA }

ensure that {

when { UE performs a TAU procedure caused by RAT change }

then { UE transmits TRACKING AREA UPDATE REQUEST with N1 mode capability set to ‘N1 mode not supported’ }

}

11.4.12.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.501 [22], subclauses 4.9.2, 5.6.1.4; TS 24.301 [21], subclauses 4.4.2.3, 5.5.3.2.2 and TS 24.229 subclause U.2.2.6.4. Unless otherwise stated these are Rel-15 requirements.

NOTE: Conformance requirements in regard to establishing an emergency call in EPS are not provided. This can be found in IMS Emergency tests specified in TS 36.523-1 [13].

[TS 24.501, subclause 4.9.2]

The UE shall only disable the N1 mode capability for 3GPP access when in 5GMM-IDLE mode.

[TS 24.501, subclause 5.6.1.4]

For case h) in subclause 5.6.1.1, the UE shall treat the indication from the lower layers when the UE has changed to S1 mode or E-UTRA connected to 5GCN (see 3GPP TS 23.502 [9]) as successful completion of the procedure and stop timer T3517.

[TS 24.301, subclause 4.4.2.3]

Secure exchange of NAS messages via a NAS signalling connection is usually established by the MME during the attach procedure by initiating a security mode control procedure. After successful completion of the security mode control procedure, all NAS messages exchanged between the UE and the MME are sent integrity protected using the current EPS security algorithms, and except for the messages specified in subclause 4.4.5, all NAS messages exchanged between the UE and the MME are sent ciphered using the current EPS security algorithms.

…

During inter-system change from N1 mode to S1 mode in 5GMM-IDLE mode, if the UE is operating in the single-registration mode and:

1) if the tracking area updating procedure is initiated as specified in 3GPP TS 24.501 [54], the UE shall transmit a TRACKING AREA UPDATE REQUEST message integrity protected with the current 5G NAS security context and the UE shall derive a mapped EPS security context (see subclause 8.6.1 of 3GPP TS 33.501 [56]). The UE shall include the eKSI indicating the 5G NAS security context value in the TRACKING AREA UPDATE REQUEST message.

After receiving the TRACKING AREA UPDATE REQUEST message including the eKSI, the MME forwards the TRACKING AREA UPDATE REQUEST message to the source AMF, if possible, to obtain the mapped EPS security context from the AMF as specified in 3GPP TS 33.501 [56]. The MME re-establishes the secure exchange of NAS messages by either:

– replying with a TRACKING AREA UPDATE ACCEPT message that is integrity protected and ciphered using the mapped EPS NAS security context. From this time onward, all NAS messages exchanged between the UE and the MME are sent integrity protected and except for the messages specified in subclause 4.4.5, all NAS messages exchanged between the UE and the MME are sent ciphered; or

[TS 24.301, subclause 5.5.3.2.2]

The UE in state EMM-REGISTERED shall initiate the tracking area updating procedure by sending a TRACKING AREA UPDATE REQUEST message to the MME,

…

z) when the UE performs inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE operates in single-registration mode, and conditions specified in 3GPP TS 24.501 [54] apply;

…

zd) when the UE performs inter-system change from N1 mode to S1 mode in EMM-CONNECTED mode.

For all cases except case b, the UE shall set the EPS update type IE in the TRACKING AREA UPDATE REQUEST message to "TA updating". For case b, the UE shall set the EPS update type IE to "periodic updating".

…

When initiating a tracking area updating procedure while in S1 mode, the UE shall use the current EPS NAS integrity key to integrity protect the TRACKING AREA UPDATE REQUEST message, unless the UE is performing inter-system change from N1 mode to S1 mode.

…

If a UE has established PDN connection(s) and uplink user data pending to be sent via user plane when it initiates the tracking area updating procedure, or uplink signalling not related to the tracking area updating procedure when the UE does not support control plane CIoT EPS optimization, 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.

…

If the UE has a current EPS security context, the UE shall include the eKSI (either KSIASME or KSISGSN) in the NAS Key Set Identifier IE in the TRACKING AREA UPDATE REQUEST message. Otherwise, the UE shall set the NAS Key Set Identifier IE to the value "no key is available". If the UE has a current EPS security context, the UE shall integrity protect the TRACKING AREA UPDATE REQUEST message with the current EPS security context. Otherwise the UE shall not integrity protect the TRACKING AREA UPDATE REQUEST message.

…

For the case z and zd, the TRACKING AREA UPDATE REQUEST message shall be integrity protected using the 5GS security context available in the UE. The UE shall include a GUTI, mapped from 5G-GUTI (see 3GPP TS 23.501 [54] and 3GPP TS 23.003 [2]), in the Old GUTI IE in the TRACKING AREA UPDATE REQUEST message. In addition, the UE shall include Old GUTI type IE with GUTI set to "Native GUTI", and the UE shall include a UE status IE with a 5GMM registration status set to "UE is in 5GMM-REGISTERED state".

When the tracking area updating procedure is initiated in EMM-IDLE mode, the UE may also include an EPS bearer context status IE in the TRACKING AREA UPDATE REQUEST message, indicating which EPS bearer contexts are active in the UE. The UE shall include the EPS bearer context status IE in TRACKING AREA UPDATE REQUEST message:

– …

– for the case z; and

…

If the UE initiates the first tracking area updating procedure following an initial registration in N1 mode and the UE is operating in the single-registration mode, the UE shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message.

…

If the UE supports NB-S1 mode, Non-IP PDN type, or N1 mode, then the UE shall support the extended protocol configuration options IE.

For all cases except case b, if the UE supports the extended protocol configuration options IE, then the UE shall set the ePCO bit to "extended protocol configuration options supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message.

…

For all cases except case b, if the UE supports dual connectivity with NR, then the UE shall set the DCNR bit to "dual connectivity with NR supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message and shall include the UE additional security capability IE in the TRACKING AREA UPDATE REQUEST message.

…

For all cases except case b, if the UE supports N1 mode, the UE shall set the N1mode bit to "N1 mode supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message and shall include the UE additional security capability IE in the TRACKING AREA UPDATE REQUEST message.

[TS 24.229, subclause U.2.2.6.4]

NOTE: This subclause covers only the case where the UE selects the IM CN subsystem in accordance with the conventions and rules specified in 3GPP TS 23.167 [4B] and describes the IP-CAN specific procedure. It does not preclude the use of CS domain. When a CS system based on 3GPP TS 24.008 [8] is to be used, clause B.5 applies.

When the UE operates in single-registration mode as described in 3GPP TS 24.501 [258] and the UE recognises that a call request is an emergency call, if:

1) the IM CN subsystem is selected in accordance with the conventions and rules specified in 3GPP TS 23.167 [4B]; and

2) the UE is currently registered to the 5GS services while the UE is in an NR cell connected to 5GCN;

then the following treatment is applied:

1) if the EMC indicates "Emergency services not supported":

…

b) if the UE supports emergency services fallback as specified in 3GPP TS 23.501 [257] and the emergency services fallback is not available (i.e., "ESFB is N" as described in 3GPP TS 23.167 [4B]) and if:

…

ii) the EMF is set to "Emergency services fallback not supported" or the UE is not capable of accessing 5GCN via E-UTRA, the UE shall disable the N1 mode capability for 3GPP access as specified in 3GPP TS 24.501 [257] and attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to establish a PDN connection for emergency bearer services; and

c) if the UE does not support emergency services fallback as specified in 3GPP TS 23.501 [257], the UE shall disable the N1 mode capability for 3GPP access as specified in 3GPP TS 24.501 [257] and attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC and the network provides the UE with the EMC BS set to "emergency bearer services in S1 mode supported" as described in 3GPP TS 24.301 [8J], the UE shall perform the procedures as described in subclause L.2.2.6 to establish a PDN connection for emergency bearer services;

11.4.12.3 Test description

11.4.12.3.1 Pre-test conditions

System Simulator:

– 2 cells

– NR Cell 1 as defined in TS 38.508-1 [4] Table 4.4.2-3. System information combination NR-6 as defined in TS 38.508-1 [4], subclause 4.4.3.1.2.

– E-UTRA Cell 1 as defined in TS 36.508 [7] Table 4.4.2-2. System information combination 31 as defined in TS 36.508 [7], subclause 4.4.3.1.1.

– Power levels are constant and as defined in Tables 11.1.10.3.1-1/2.

Table 11.4.12.3.1-1: Time instances of cell power level and parameter changes for FR1

Parameter name

Unit

NR Cell 1

E-UTRA Cell 1

Remark

T0

SS/PBCH SSS EPRE

dBm/SCS

-88

–

RS EPRE

dBm/15kHz

–

-91

Table 11.4.12.3.1-2: Time instances of cell power level and parameter changes for FR2

Parameter name

Unit

NR Cell 1

E-UTRA Cell 1

Remark

T0

SS/PBCH SSS EPRE

dBm/SCS

-82

–

RS EPRE

dBm/15kHz

–

-91

UE:

None.

Preamble:

– With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state RRC_IDLE using generic procedure parameters Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On) in accordance with the procedure described in TS 38.508-1 [4], clause 4.5.2. 4G GUTI and eKSI are assigned and security context established.

– the UE is switched-off.

– With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state 1N-A, NR RRC_IDLE Connectivity (NR) in accordance with the procedure described in TS 38.508-1 [4], Table 4.5.4.2-2. 5G-GUTI and ngKSI are assigned and security context established.

11.4.12.3.2 Test procedure sequence

Table 11.4.12.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

0

Set the power levels according to “T0” as per Table 11.4.12.3.1-1/2

–

–

–

–

1

Make the UE initiate an Emergency call.

–

–

–

–

2

Check: Does the UE transmit an RRCConnectionRequest message with ‘establishmentCause’ set to ’emergency’ on E-UTRA cell 1?

–>

RRC: RRCConnectionRequest

1

P

3

SS transmits an RRCConnectionSetup message.

<–

RRC: RRCConnectionSetup

–

–

4

Check: Does the UE transmit an RRCConnectionSetupComplete message to confirm the successful completion of the connection establishment and a TRACKING AREA UPDATE REQUEST message is sent to update the registration of the actual tracking area.

For some consequences related to the content of the TRACKING AREA UPDATE REQUEST message see the Notes in TS.36.508 [7], Table 4.5A.2.1-1.

–>

RRC: RRCConnectionSetupComplete NAS: TRACKING AREA UPDATE REQUEST

2

P

5-8

Steps 5-8 from the Generic Test Procedure for IMS Emergency call establishment in EUTRA: Normal Service as specified in TS 36.508 [7], Table 4.5A.4.3-1 are performed.

–

–

–

–

9

SS responds with TRACKING AREA UPDATE ACCEPT message.

<–

RRC: DLInformationTransfer

NAS: TRACKING AREA UPDATE ACCEPT

–

–

10

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

–>

RRC: ULInformationTransfer

NAS: TRACKING AREA UPDATE COMPLETE

–

–

11-17

Steps 9-15 from the Generic Test Procedure for IMS Emergency call establishment in EUTRA: Normal Service as specified in TS 36.508 [7], Table 4.5A.4.3-1 are performed.

–

–

–

–

18

The SS waits 1 second.

–

–

–

–

19

Release IMS Call as specified in the generic procedure in TS 34.229-1 [35] subclause C.32.

–

–

–

–

11.4.12.3.3 Specific message contents

Table 11.4.12.3.3-1: REGISTRATION REQUEST (Preamble; TS 38.508-1 [4], Table 4.5.2.2-2)

Derivation Path: TS 38.508-1 [4], Table 4.7.1-6

Information Element

Value/remark

Comment

Condition

5GMM capability

S1 mode (octet 3, bit 1)

‘1’B

S1 mode supported

Table 11.4.12.3.3-2: REGISTRATION ACCEPT (Preamble; TS 38.508-1 [4], Table 4.5.2.2-2)

Derivation path: TS 38.508-1 [4], Table 4.7.1-7

Information Element

Value/remark

Comment

Condition

5GS network feature support

Emergency service support indicator for 3GPP access (EMC) (octet 3, bit 3 and bit 4)

’00’B

Emergency services not supported

Emergency service fallback indicator for 3GPP access (EMF) (octet 3, bit 5 and bit 6)

’00’B

Emergency services fallback not supported

Table 11.4.12.3.3-3: RRCConnectionRequest (step 2, table 11.4.12.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.6.1-16

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r8 SEQUENCE {

establishmentCause

emergency

}

}

}

Table 11.4.12.3.3-4: TRACKING AREA UPDATE REQUEST (step 4, Table 11.4.12.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.7.2-27

Information Element

Value/remark

Comment

Condition

UE network capability

NR

All octets with the exception of octet 8, bit 8 and octet 9, bit 6

Any allowed value

Extended protocol configuration options (ePCO) (octet 8, bit 8)

1

ePCO supported

N1 mode supported (N1mode) (octet 9, bit 6)

0

N1 mode

not supported

Table 11.4.12.3.3-5: Message PDN CONNECTIVITY REQUEST (step 11, Table 11.4.12.3.2-1)

Derivation Path: TS 36.508 [7], Table 4.7.2-1.

Information Element

Value/Remark

Comment

Condition

Request type

‘0100’B

emergency

Access point name

Not present

Table 11.4.12.3.3-6: Message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST (step 12, Table 11.4.12.3.2-1)

Derivation path: TS 36.508 [7], Table 4.7.3-6 and table 4.6.1-8 with condition UM-DRB-ADD(2).

Information Element

Value/Remark

Comment

Condition

EPS bearer identity

an additional EPS Bearer Id different from default EPS Bearer Id or/and any mapped EPS bearer

Access point name

sos

APN value as recommended by IR.88 clause 6.4 [39]