## 6.4.1.3 UE-requested PDU session establishment procedure accepted by the network (FF)
- TP_5GNAS_AMF_UPE_ACC_01
- Verify that the IUT, upon receiving the PDU SESSION ESTABLISHMENT REQUEST from the UE with correct data and with type initial request, sends PDU SESSION ESTABLISHMENT ACCEPT meesage
## 6.4.1.7 Abnormal cases on the network side (FF)
- TP_5GNAS_AMF_UPE_ABN_01
- Verify that the IUT sends a PDU SESSION ESTABLISHMENT REJECT with cause #31 (request rejected, unspecified), when the UE sends a PDU SESSION ESTABLISHMENT REQUEST with type initial emergency request and there is already a emergency PDU session for the UE.
Note: possible, that the IUT releases the existing emergency session and don't sends a REJECT. Maybe implementation-dependend?
- TP_5GNAS_AMF_UPE_ABN_02
- Verify that the IUT sends a PDU SESSION ESTABLISHMENT REJECT with cause #54 (PDU session does not exist), when the UE sends a PDU SESSION ESTABLISHMENT REQUEST with type existing PDU session and there is no PDU session with that ID.
- TP_5GNAS_AMF_UPE_ABN_03
- Verify that the IUT sends a PDU SESSION ESTABLISHMENT REJECT with cause #29 (user authentication or authorization failed), when the UE sends a PDU SESSION ESTABLISHMENT REQUEST with type initial request and the provided authentication and authorization data don't match local policy and user's subscription data.
## 6.3.1.1 (FF)
- TP_5GNAS_AMF_UPA_ACC_01
- Verify that the IUT, upon receiving the PDU SESSION AUTHENTICATION COMPLETE Message after completing the PDU session authentication and authorization procedure, successfully completes the process by sending PDU SESSION ESTABLISHMENT ACCEPT.
## 6.3.1.2.3 Abnormal cases on the network side (FF)
TP_5GNAS_AMF_UPA_ABN_01
- Verify that the IUT retransmits PDU SESSION AUTHENTICATION COMMAND message after timer T3590 expiration first time.
TP_5GNAS_AMF_UPA_ABN_02
- Verify that the IUT aborts the procedure after timer T3590 expiration four times.
## 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.
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.
- 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 (FF)
## 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).
@@ -207,11 +212,14 @@ Note: possible, that the IUT releases the existing emergency session and don't s
Note: possible to test? In this case the IUT can't be triggered with a (interface) message.
## 6.4.2.4.1 UE-requested PDU session modification procedure not accepted by the network (FF)
- TP_5GNAS_AMF_UPN_REJ_01
- Verify that 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).
- TP_5GNAS_AMF_UPN_REJ_02
- Verify that 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).
- TP_5GNAS_AMF_UPN_REJ_03
- Verify that 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).
- TP_5GNAS_AMF_UPN_REJ_04
- Verify that 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).
