4.9.17 Test procedure for IMS MO call release in 5GC
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
4.9.17.1 Scope
The purpose of this procedure is to make a UE initiated release of an ongoing IMS call.
4.9.17.2 Procedure description
4.9.17.2.1 Initial conditions
System Simulator:
– 1 NR Cell connected to 5GC, default parameters.
User Equipment:
– The UE is in state 3N-A on the NR Cell with an active IMS call.
4.9.17.2.2 Procedure sequence
Table 4.9.17.2.2-1: IMS MO call release in 5GC
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1-2 |
Generic test procedure for MO release of speech call, steps 1-2, as defined in annex A.7 of TS 34.229-5 [47] are performed. |
– |
– |
– |
– |
|
3 |
The SS transmits an RRCReconfiguration message and an PDU SESSION MODIFICATION COMMAND |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
– |
EXCEPTION: Steps 4 and 5 can occur in any order. |
– |
– |
– |
– |
|
4 |
The UE transmits an RRCReconfigurationComplete message |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
5 |
Check: Does the UE transmit a ULInformationTransfer message, an UL NAS TRANSPORT message and an PDU SESSION MODIFICATION COMPLETE message? |
–> |
NR RRC: ULInformationTransfer 5GMM: UL NAS TRANSPORT 5GSM: PDU SESSION MODIFICATION COMPLETE |
– |
P |
4.9.17.2.3 Specific message contents
Table 4.9.17.2.3-1: RRCReconfiguration (step 3, Table 4.9.17.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 |
IMS_VOICE |
||
|
DRB-Identity[1] |
DRB-Identity linked to the IMS speech bearer |
entry 1 |
||
|
} |
||||
|
drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity { |
2 entries |
IMS_VIDEO |
||
|
DRB-Identity[1] |
DRB-Identity linked to the IMS video bearer |
entry 1 |
||
|
DRB-Identity[2] |
DRB-Identity linked to the IMS video bearer |
entry 2 |
||
|
} |
||||
|
} |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
masterCellGroup SEQUENCE { |
||||
|
rlc-BearerToReleaseList SEQUENCE (SIZE (1..maxLC-ID)) OF LogicalChannelIdentity { |
1 entry |
IMS_VOICE |
||
|
LogicalChannelIdentity[1] |
Same value as drb-Identity[1] above |
entry 1 |
||
|
} |
||||
|
rlc-BearerToReleaseList SEQUENCE (SIZE (1..maxLC-ID)) OF LogicalChannelIdentity { |
2 entries |
IMS_VIDEO |
||
|
LogicalChannelIdentity[1] |
Same value as drb-Identity[1] above |
entry 1 |
||
|
LogicalChannelIdentity[2] |
Same value as drb-Identity[2] above |
entry 2 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
Condition |
Explanation |
|
IMS_VOICE |
If this QoS rule is used to setup an IMS voice session |
|
IMS_VIDEO |
If this QoS rule is used to setup an IMS video session |
Table 4.9.17.2.3-2: PDU SESSION MODIFICATION COMMAND (step 3, Table 4.9.17.2.2-1)
|
Derivation Path: Table 4.7.2-9. |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
PDU session ID |
Same value as sent in PDU SESSION ESTABLISHMENT REQUEST message. |
|||
|
Authorized QoS rules |
||||
|
QoS rule[1] |
IMS_VOICE, IMS_VIDEO |
|||
|
QoS rule identifier |
‘00000011’B |
QoS rule 3 |
||
|
Rule operation code |
‘010’B |
Delete existing QoS rule |
||
|
QoS rule[2] |
IMS_VIDEO |
|||
|
QoS rule identifier |
‘00000100’B |
QoS rule 4 |
||
|
Rule operation code |
‘010’B |
Delete existing QoS rule |
||
|
Authorized QoS flow descriptions |
||||
|
QoS flow descriptions[1] |
IMS_VOICE, IMS_VIDEO |
|||
|
QFI |
‘00000111’B |
QFI 7 |
||
|
Operation code |
‘010’B |
Delete existing QoS flow |
||
|
QoS flow descriptions[2] |
IMS_VIDEO |
|||
|
QFI |
’00001000’B |
QFI 8 |
||
|
Operation code |
‘010’B |
Delete existing QoS flow |
||
|
Condition |
Explanation |
|
IMS_VOICE |
If this QoS rule is used to setup an IMS voice session |
|
IMS_VIDEO |
If this QoS rule is used to setup an IMS video session |