## 6.4.2.4.1 UE-requested PDU session modification procedure not accepted by the network (FF)
- TP_5GNAS_AMF_UPN_REJ_01
- Verify the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request of LADN modification and UE outside service area, sends a SESSION MODIFICATION REJECT with reason #46 (out of LADN service area).
- Verify the IUT, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request of LADN modification and UE outside service area, sends a SESSION MODIFICATION REJECT with reason #46 (out of LADN service area).
- TP_5GNAS_AMF_UPN_REJ_02
- Verify the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request for a not supported service by the PLMN, sends a SESSION MODIFICATION REJECT with reason #32 (Service option not supported).
- Verify the IUT, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request for a not supported service by the PLMN, sends a SESSION MODIFICATION REJECT with reason #32 (Service option not supported).
- TP_5GNAS_AMF_UPN_REJ_03
- Verify the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request including a PTI that is already in use, sends a SESSION MODIFICATION REJECT with reason #35 (PTI already in use).
- Verify the IUT, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request including a PTI that is already in use, sends a SESSION MODIFICATION REJECT with reason #35 (PTI already in use).
- TP_5GNAS_AMF_UPN_REJ_04
- Verify the UE, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request for a wrong 5QI, sends a SESSION MODIFICATION REJECT with reason #59 (Unsupported 5QI value).
- Verify the IUT, upon receiving a PDU SESSION MODIFICATION REQUEST by the UE with a request for a wrong 5QI, sends a SESSION MODIFICATION REJECT with reason #59 (Unsupported 5QI value).
## 6.4.3.2, 6.4.3.4 (FF)
- TP_5GNAS_AMF_UPR_REJ_01
- Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST by the UE and not accepts the session release with reason #35 (PTI already in use).
- TP_5GNAS_AMF_UPR_REJ_02
- Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST by the UE and not accepts the session release with reason #43 (Invalid PDU session identity).
Note: there can be other protocol reasons for not accepting the PDU Session release
## 6.4.3.6 Abnormal cases on the network side (FF)
- TP_5GNAS_AMF_UPR_ABN_01
- Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST with a wrong PDU Sesiion ID by the UE and not accepts the session release with reason #43 (Invalid PDU session identity).
# TP objectives ideas
## 6.4.3.2, 6.4.3.4 (FF)
- TP_5GNAS_AMF_UPR_ACC_01
- Verify that the IUT handles correctly a PDU SESSION RELEASE REQUEST after receiving a PDU SESSION RELEASE REQUEST by the UE.
- Verify that the IUT handles correctly a PDU session release after receiving a PDU SESSION RELEASE REQUEST by the UE.
Note: There is no message back to the UE after receiving the PDU SESSION RELEASE REJECT, the correct execution of Session Release can be tested with another message.
[KSCH] Hard to understand. Do you mean the fact that there is no "PDU SESSION RELEASE CONFIRM" to acknowledge a UE Initialted "PDU SESSION RELEASE REQUEST". Think SMF has to send PDU SESSION RELEASE COMMAND after reception of UE Initiated Release Request to complete the release procedure.
[stl] Answer: As far as i understand the PDU SESSION RELEASE COMMAND is only used in cases where the SMF initiates the PDU session release. This testcase deals with a UE initiated session release. My understanding from the base spec is: SMF will release the session without any further interaction with the UE. It should be possible to verify the correct session release by using another message that try to use this not longer existing PDU session. But I left that out on purpose for the TO (only as note) because i think the real check in the end should not be part of the TO.
- TP_5GNAS_AMF_UPR_REJ_01
- Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST by the UE and not accepts the session release with reason #35 (PTI already in use).
- TP_5GNAS_AMF_UPR_REJ_02
- Verify that the IUT sends correctly a PDU SESSION RELEASE REJECT after receiving a PDU SESSION RELEASE REQUEST by the UE and not accepts the session release with reason #43 (Invalid PDU session identity).
Note: there can be other protocol reasons for not accepting the PDU Session release
