4.9.12 Test procedure for IMS Emergency call establishment in 5GC without IMS emergency registration
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
4.9.12.1 Scope
This procedure aims at verifying the UE establishment of IMS Emergency call in 5GC without the need for IMS emergency registration to take place beforehand e.g. under Limited Service or SIM/USIM not available, the SIM/USIM is considered invalid by the UE conditions.
4.9.12.2 Procedure description
4.9.12.2.1 Initial conditions
System Simulator:
– 1 NR Cell connected to 5GC, default parameters unless specified otherwise. PLMN/TAI which the cell belongs to, shall be explicitly specified in the TC which calls the procedure in its entirety or refers to parts of it
User Equipment:
– Whether the Test UICC shall be inserted or not, and, its settings e.g. in regard to the provision of Emergency Numbers, shall be explicitly specified in the TC which calls the procedure in its entirety or refers to parts of it.
4.9.12.2.2 Procedure sequence
Table 4.9.12.2.2-1: Test procedure sequence UE IMS Emergency call establishment in 5GC without IMS emergency registration
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message/PDU/SDU |
||||
– |
EXCEPTION: Unless otherwise stated all the messages below are transmitted on the cell specified in the test case. |
– |
– |
– |
– |
1 |
Check: Does the UE transmits an RRCSetupRequest message with ‘establishmentCause’ set to ’emergency’? |
–> |
NR RRC: RRCSetupRequest |
– |
P |
2 |
The SS transmits an RRCSetup message. |
<– |
NR RRC: RRCSetup |
– |
– |
3 |
Check: Does the UE transmits an RRCSetupComplete message and a REGISTRATION REQUEST message with ‘Service type’ set to ’emergency services’? |
–> |
NR RRC: RRCSetupComplete 5GMM: REGISTRATION REQUEST |
– |
P |
4 |
The SS transmits a DLInformationTransfer message and a SECURITY MODE COMMAND message with ‘Selected NAS security algorithms’ set to "null integrity protection algorithm" (5G-IA0), "null ciphering algorithm" (5G-EA0). |
<– |
NR RRC: DLInformationTransfer 5GMM: SECURITY MODE COMMAND |
– |
– |
5 |
The UE transmits an ULInformationTransfer message and a SECURITY MODE COMPLETE message. |
–> |
NR RRC: ULInformationTransfer 5GMM: SECURITY MODE COMPLETE |
– |
P |
6 |
The SS transmits a SecurityModeCommand message with cipheringAlgorithm set to ‘NULL‘ ciphering algorithm (nea0) and integrityProtAlgorithm set to ‘NULL‘ integrity protection algorithm (nia0). |
<– |
NR RRC: SecurityModeCommand |
– |
– |
7 |
The UE transmits a SecurityModeComplete message. |
–> |
NR RRC: SecurityModeComplete |
– |
P |
8 |
The SS transmits a UECapabilityEnquiry message. |
<– |
NR RRC: UECapabilityEnquiry |
– |
– |
9 |
The UE transmits a UECapabilityInformation message. |
–> |
NR RRC: UECapabilityInformation |
– |
– |
10 |
The SS transmits a DLInformationTransfer message and a REGISTRATION ACCEPT message. |
<– |
NR RRC: DLInformationTransfer 5GMM: REGISTRATION ACCEPT |
– |
– |
11 |
The UE transmits an ULInformationTransfer message and a REGISTRATION COMPLETE message. |
–> |
NR RRC: ULInformationTransfer 5GMM: REGISTRATION COMPLETE |
– |
– |
12 |
Void |
– |
– |
– |
– |
13 |
Check: Does the UE transmits an UL NAS TRANSPORT message with ‘Request type’ set to ‘initial emergency request’, and, a PDU SESSION ESTABLISHMENT REQUEST? |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT REQUEST |
– |
P |
– |
EXCEPTION: In parallel to the events described in steps 14-15 below the events specified in steps 1a1 of Table 4.9.12.2.2-2 take place. |
– |
– |
– |
– |
14 |
The SS transmits an RRCReconfiguration message and an PDU SESSION ESTABLISHMENT ACCEPT to establish SRB2 and DRB. |
<– |
NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION ESTABLISHMENT ACCEPT |
– |
– |
15 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
– |
EXCEPTION: In parallel to the events described in steps 16-18 below the events specified in steps 2 of Table 4.9.12.2.2-2 take place. |
– |
– |
– |
– |
16 |
The SS transmits an RRCReconfiguration message and an PDU SESSION MODIFICATION COMMAND. |
<– |
NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMMAND |
– |
– |
– |
EXCEPTION: Depending upon UE implementation, steps 17 and 18 can occur in any order. |
– |
– |
– |
– |
17 |
The UE transmits an RRCReconfigurationComplete message. |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
18 |
Check: Does the UE transmits an ULInformationTransfer message and an PDU SESSION MODIFICATION COMPLETE message? |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
P |
Table 4.9.12.2.2-2: IMS signalling and Emergency call establishment
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message/PDU/SDU |
||||
– |
EXCEPTION: Step 1a1 describes behaviour depending UE implementation; the "lower case letter" identifies a step sequence that take place if the UE performs a specific action. |
– |
– |
– |
– |
1a1 |
The generic procedure for IP address allocation in the user plane specified in subclause 4.5A.3 takes place. |
– |
– |
– |
– |
2 |
Generic test procedure for setting up IMS Emergency Voice Call as defined in TS 34.229-5 [47] annex A.6 is performed. |
– |
– |
– |
– |
4.9.12.2.3 Specific Message content
All specific message contents shall be according subclause 4.6 and 4.7 with the exceptions below.
NOTE: Some of the specific message contents provided below assume that the UE is in the state 5GMM-DEREGISTERED.LIMITED-SERVICE or 5GMM-REGISTERED.LIMITED-SERVICE (e.g. the selected cell over 3GPP access is in a forbidden PLMN or is in a forbidden tracking area respectively), or, in 5GMM-DEREGISTERED.NO-SUPI as defined in TS 24.501 [28], subclauses 5.1.3.2.1.3.3 and 5.1.3.2.1.3.6 respectively. All necessary details required shall be explicitly specified in the TC which calls the procedure in its entirety or refers to parts of it.
Table 4.9.12.2.3-1: SIB1 (at any time prior and during the procedure, Table 4.9.12.2.2-1)
Derivation Path: Table 4.6.1-28. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SIB1 ::= SEQUENCE { |
||||
ims-EmergencySupport |
Present |
true |
||
} |
Table 4.9.12.2.3-2: RRCSetupRequest (step 1, Table 4.9.12.2.2-1)
Derivation Path: Table 4.6.1-23. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCSetupRequest ::= SEQUENCE { |
||||
rrcSetupRequest SEQUENCE { |
||||
establishmentCause |
emergency |
|||
} |
||||
} |
Table 4.9.12.2.3-3: REGISTRATION REQUEST (step 3, Table 4.9.12.2.2-1)
Derivation Path: Table 4.7.1-6, condition EMERGENCY. |
Table 4.9.12.2.3-4: SECURITY MODE COMMAND (step 4, Table 4.9.12.2.2-1)
Derivation Path: Table 4.7.1-25. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Selected NAS security algorithms |
||||
Type of ciphering algorithm |
5G-EA0 |
null ciphering algorithm |
||
Type of integrity protection algorithm |
5G-IA0 |
null integrity protection algorithm |
||
ngKSI |
||||
NAS key set identifier |
‘000’B |
Table 4.9.12.2.3-5: SecurityModeCommand (step 6, Table 4.9.12.2.2-1)
Derivation Path: Table 4.6.1-25. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SecurityModeCommand ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
securityModeCommand SEQUENCE { |
||||
securityConfigSMC SEQUENCE { |
||||
securityAlgorithmConfig SEQUENCE { |
||||
cipheringAlgorithm |
nea0 |
‘NULL‘ ciphering algorithm |
||
integrityProtAlgorithm |
nia0 |
‘NULL‘ integrity protection algorithm |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 4.9.12.2.3-6: REGISTRATION ACCEPT (step 10, Table 4.9.12.2.2-1)
Derivation Path: Table 4.7.1-7, condition EMERGENCY. |
Table 4.9.12.2.3-7: UL NAS TRANSPORT (step 13, Table 4.9.12.2.2-1)
Derivation Path: Table 4.7.1-10, condition INITIAL_PDU_REQUEST. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Request type |
‘011’B |
initial emergency request |
||
S-NSSAI |
Not Present |
|||
DNN |
Not Present |
Table 4.9.12.2.3-8: PDU SESSION ESTABLISHMENT REQUEST (step 13, Table 4.9.12.2.2-1)
Derivation Path: Table 4.7.2-1. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
PDU session ID |
A value that is not currently being used by another PDU session |
|||
PTI |
A value currently not used |
|||
SSC mode |
‘001’B |
SSC mode 1 |
Table 4.9.12.2.3-9: DL NAS TRANSPORT (step 14, Table 4.9.12.2.2-1)
Derivation Path: Table 4.7.1-11, condition 5GSM_MESSAGE. |
Table 4.9.12.2.3-10: PDU SESSION ESTABLISHMENT ACCEPT (step 14, Table 4.9.12.2.2-1)
Derivation Path: Table 4.7.2-2. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Selected SSC mode |
‘001’B |
SSC mode 1 |
||
Authorized QoS rules |
Reference QoS rule #2 as defined in Table 4.8.2.1-2. |
|||
Authorized QoS flow descriptions |
Reference QoS flow #2 as defined in Table 4.8.2.3-2. |
Table 4.9.12.2.3-11: RRCReconfiguration (step 14, Table 4.9.12.2.2-1)
Derivation Path: Table 4.8.1-1: RRCReconfiguration-SRB2-DRB (1, 0) |
Table 4.9.12.2.3-12: PDU SESSION MODIFICATION COMMAND (step 16, Table 4.9.12.2.2-1)
Derivation Path: Table 4.7.2-2. |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
PDU session ID |
Same value as sent in PDU SESSION ESTABLISHMENT REQUEST message. |
|||
Authorized QoS rules |
Reference QoS rule #7 as defined in Table 4.8.2.1-7 using condition IMS_VOICE. |
|||
Authorized QoS flow descriptions |
Reference QoS flow #5 as defined in Table 4.8.2.3-5. |
Table 4.9.12.2.3-13: RRCReconfiguration (step 16, Table 4.9.12.2.2-1)
Derivation Path: 4.8.1-1C RRCReconfiguration-Speech |
Table 4.9.12.2.3-14: INVITE (step 2, Table 4.9.12.2.2-2)
Derivation Path: TS 34.229-5 [47], Annex A.6, Step 1 with conditions A6 and A28 |