4.9.12B Test procedure for IMS MT Emergency call release
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
4.9.12B.1 Scope
This procedure aims at verifying the network initiated release of an ongoing IMS Emergency call in 5GC
The procedure provides different handling options of the emergency PDU session based on the condition parameter defined in Table 4.9.12B.1-1.
Table 4.9.12B.1-1: Condition parameters
|
Condition |
Explanation |
|
release emergency PDU session |
When this parameter is present the SS will release the emergency PDU session after the release of the emergency call |
|
keep emergency PDU session |
When this parameter is present the SS will release the voice QoS, but not release the emergency PDU session after the release of the emergency call |
|
NOTE 1: If the defined condition parameter is not present when the procedure is referred to then the default value ‘release emergency PDU session’ will apply |
|
4.9.12B.2 Procedure description
4.9.12B.2.1 Initial conditions
System Simulator:
– 1 NR Cell connected to 5GC, default parameters.
User Equipment:
– The Test UICC shall be inserted. It shall provide Emergency Numbers.
The procedure assumes that the UE is in test state 3N-A, subclause 4.4A.2 on the NR Cell with an active IMS emergency call. All necessary details required shall be explicitly specified in the TC which calls the procedure in its entirety or refers to parts of it.
4.9.12B.2.2 Procedure sequence
Table 4.9.12B.2.2-1: Test procedure sequence IMS MT Emergency call release
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message/PDU/SDU |
||||
|
1-2 |
Generic test procedure for MT release of speech call, steps 1-2, as defined in Annex A.8 of TS 34.229-5 [47] is performed. |
– |
– |
– |
– |
|
– |
EXCEPTION: Steps 3a1 – 3b3 describe a step sequence depending on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value |
– |
– |
– |
– |
|
3a1 |
IF ‘release emergency PDU session’ THEN test procedure for PDU Session Release specified in subclause 4.9.21 takes place. |
– |
– |
||
|
3b1 |
ELSE (i.e. ‘Keep emergency PDU session’) THEN the SS transmits a RRCReconfiguration message and a PDU SESSION MODIFICATION COMMAND message. |
<– |
NR RRC: RRCReconfiguration 5GMM: DL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMMAND |
– |
– |
|
– |
EXCEPTION: Steps 3b2 and 3b3 can occur in any order. |
– |
– |
– |
– |
|
3b2 |
The UE transmits a RRCReconfigurationComplete |
– |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
3b3 |
Check: Does the UE transmit a PDU SESSION MODIFICATION COMPLETE message? |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
P |
|
4 |
Void |
||||
4.9.12B.2.3 Specific Message content
All specific message contents shall be according subclause 4.6 and 4.7 with the exceptions below.
Table 4.9.12B.2.3-1: RRCReconfiguration (step 3a1, Table 4.9.12B.2.2-1; step 1 Table 4.9.21.2.2-1)
|
Derivation Path: Table 4.6.1-13. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
radioBearerConfig SEQUENCE { |
||||
|
drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity { |
2 entries |
|||
|
DRB-Identity[1] |
DRB-Identity linked to the IMS emergency signalling bearer |
entry 1 |
||
|
DRB-Identity[2] |
DRB-Identity linked to the IMS emergency speech bearer |
entry 2 |
||
|
} |
||||
|
} |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup SEQUENCE { |
||||
|
rlc-BearerToReleaseList SEQUENCE (SIZE (1..maxLC-ID)) OF LogicalChannelIdentity { |
2 entries |
|||
|
LogicalChannelIdentity[1] |
Same value as drb-Identity[1] above |
entry 1 |
||
|
LogicalChannelIdentity[2] |
Same value as drb-Identity[2] above |
entry 2 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 4.9.12B.2.3-2: PDU SESSION RELEASE COMMAND (step 3a1, Table 4.9.12B.2.2-1; step 1 Table 4.9.21.2.2-1)
|
Derivation Path: Table 4.7.1-14. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Set according to the Emergency session ID. |
|||
|
5GSM cause |
‘0010 0100’B |
Regular deactivation |
||
Table 4.9.12B.2.3-3: RRCReconfiguration (step 3b1, Table 4.9.12B.2.2-1)
|
Derivation Path: Table 4.6.1-13. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
radioBearerConfig SEQUENCE { |
||||
|
drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity { |
1 entry |
|||
|
DRB-Identity |
DRB-Identity linked to the IMS speech bearer |
|||
|
} |
||||
|
} |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup SEQUENCE { |
||||
|
rlc-BearerToReleaseList SEQUENCE (SIZE (1..maxLC-ID)) OF LogicalChannelIdentity { |
1 entry |
|||
|
LogicalChannelIdentity |
Same value as drb-Identity above |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 4.9.12B.2.3-4: PDU SESSION MODIFICATION COMMAND (step 3b1, Table 4.9.12B.2.2-1)
|
Derivation Path: Table 4.7.2-9. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Set according to the Emergency session ID |
|||
|
Authorized QoS rules |
||||
|
QoS rule |
||||
|
QoS rule identifier |
‘00000011’B |
QoS rule 3 |
||
|
Rule operation code |
‘010’B |
Delete existing QoS rule |
||
|
Authorized QoS flow descriptions |
||||
|
QoS flow descriptions |
||||
|
QFI |
‘00000111’B |
QFI 7 |
||
|
Operation code |
‘010’B |
Delete existing QoS flow |
||